You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Does Cyclone Scheme have a method of handling dates and times beyond (current-seconds)?
I've scoured the documentation but there doesn't appear to be any way to format an ISO 8601 compliant date string (eg YYYY-MM-DD HH:MM) using the built-in libraries, or anything available in Winds.
I'm enjoying using Cyclone and it's speed and portability, but I'm not interested in rolling my own bug-ridden date library. Obviously I could download the code for SRFI-19 myself and use that, but it would be nice if this basic functionality was smoothy implemented out of the box.
Thanks for creating a great -- and super well documented!! -- implementation!
The text was updated successfully, but these errors were encountered:
I agree it would be nice if this was provided. The issue is that support has not been added for many libraries, such as SRFI-19. Still, it there is a reference implementation of that SRFI and it should be possible to port that to a library: https://github.com/scheme-requests-for-implementation/srfi-19
Once there is a working library we can make that available via Winds like many of the other SRFI's that have been ported. Do you have any interest in doing a first-cut of organizing the SRFI code into a library?
Hi! Does Cyclone Scheme have a method of handling dates and times beyond
(current-seconds)
?I've scoured the documentation but there doesn't appear to be any way to format an ISO 8601 compliant date string (eg
YYYY-MM-DD HH:MM
) using the built-in libraries, or anything available in Winds.It also appears that SRFI-19 is not supported.
Am I missing something?
I'm enjoying using Cyclone and it's speed and portability, but I'm not interested in rolling my own bug-ridden date library. Obviously I could download the code for SRFI-19 myself and use that, but it would be nice if this basic functionality was smoothy implemented out of the box.
Thanks for creating a great -- and super well documented!! -- implementation!
The text was updated successfully, but these errors were encountered: