Re: openssl eggs: current-milliseconds -> current-process-milliseconds

[siiky]

> Then my egg would be listed as a 5 egg, but would only be usable by a 
> subset of the 5.X versions.  If that is accepted, then I wonder what 
> information the major and minor versions of chicken-core convey.
>
> To me, a deprecation has a meaning when it provides a way forward, so I 
> think I agree with Mario when he says that this deprecation came in too 
> late for 5.X and too early for 6.X.

I don't disagree that it could've been done a different way, probably 
better.

But eggs have to work with CHICKEN, not the other way around. So for me 
it doesn't matter much whether current-milliseconds should or 
shouldn't've been deprecated in 5.3, but that as an egg author I have 
this choice to support more users or not, because that's the current 
situation.

Hopefully that clarifies my replies. I'm not that interested in what 
"could've been", I'm more interested in "what is" and "what will be" :)