> >> If breaking 5.X | X < latest is a concern, this means
> >> current-milliseconds must stay in 6.x and can only be removed in
> >> 7.x?
> >
> > Hm I don't see how that follows. Removing current-milliseconds in 6.x
> > doesn't break anything 5.x.
>
> Right, but just because that's already kinda b
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
On Feb 22 2023, 12:17 UTC, siiky wrote:
Hiya,
heh - I don't like to see deprecation warnings when I build stuff :)
Me neither, but I like it even less when stuff stops working (like
Doom Emacs just today)
I don't know what's the support policy for older releases in the 5.x
series, but by
It's not that simple, as using current-process-milliseconds would break
things for people using CHICKEN 5.2 or earlier.
Yeah, that's exactly the problem for me, I don't want stuff to break for
people using 5.2.
People using CHICKEN from Debian stable, for example, get CHICKEN 5.2.
It was a
However, personally, I don't see the advantage of using
current-milliseconds over current-process-milliseconds in eggs. As of
now, both calls work, the userbase is already small, and the amount of
available libraries is also not huge (comparing to popular languages).
Why should I artificially r
On Wed, 22 Feb 2023 12:17:23 + siiky wrote:
>> I don't know what's the support policy for older releases in the 5.x
>> series, but by your logic, no egg at all can use
>> current-process-milliseconds for the same reason of it not being
>> available before 5.3.
>
> AFAIK there's no hard set o
3. Use some convoluted cond-expand clause to match against values of X
(as in 5.X) as an attempt to prevent the deprecation warning and
undefined variable errors.
Don't want to pull anyone into an NPM here, but we could have a tiny egg
to abstract that away ("we" = anyone willing): expo
Hiya,
heh - I don't like to see deprecation warnings when I build stuff :)
Me neither, but I like it even less when stuff stops working (like Doom
Emacs just today)
I don't know what's the support policy for older releases in the 5.x
series, but by your logic, no egg at all can use
curren
Hi Pietro,
On Tue, 21 Feb 2023 10:23:05 + Pietro Cerutti wrote:
> On Feb 21 2023, 10:13 UTC, siiky wrote:
>
>>If you don't mind me asking, why?
>
> heh - I don't like to see deprecation warnings when I build stuff :)
>
>> From my understanding (disclaimer: not a maintainer of the openssl
>>
On Feb 21 2023, 10:13 UTC, siiky wrote:
Hi Pietro,
If you don't mind me asking, why?
heh - I don't like to see deprecation warnings when I build stuff :)
From my understanding (disclaimer: not a maintainer of the openssl egg
nor CHICKEN core maintainer), I think current-milliseconds can sta
Hi Pietro,
If you don't mind me asking, why?
From my understanding (disclaimer: not a maintainer of the openssl egg
nor CHICKEN core maintainer), I think current-milliseconds can stay for
now. current-milliseconds has been deprecated in 5.3 but hasn't been
removed yet, it's an "alias" for cur
Hi,
can anybody please s/current-milliseconds/current-process-milliseconds/
in openssl.socket.scm?
Thanks!
--
Pietro Cerutti
I have pledged to give 10% of income to effective charities
and invite you to join me - https://givingwhatwecan.org
12 matches
Mail list logo
