Matt Gushee writes:
> Hmm ...
>
> On Sun, Oct 13, 2013 at 11:11 AM, John J Foerch
> wrote:
>
>> I noticed that srfi-19-date (version 3.3.4) does not export 'date?'. I
>> think that perhaps it should.
>
> On my system:
>
> csi> (use srfi-19)
> ; loading /usr/lib/chicken/6/srfi-19.import.so ...
>
Hmm ...
On Sun, Oct 13, 2013 at 11:11 AM, John J Foerch wrote:
> I noticed that srfi-19-date (version 3.3.4) does not export 'date?'. I
> think that perhaps it should.
On my system:
csi> (use srfi-19)
; loading /usr/lib/chicken/6/srfi-19.import.so ...
; loading /usr/lib/chicken/6/srfi-19-time
Hello,
I noticed that srfi-19-date (version 3.3.4) does not export 'date?'. I
think that perhaps it should. Also, 'date?' is not documented in the
egg docs (http://wiki.call-cc.org/eggref/4/srfi-19).
Thank you,
--
John Foerch
___
Chicken-users mai
On Linux (Ubuntu 2.6.32-31 32 bit) I get the error seen below. Oddly
enough srfi-19 installed fine on chicken-iup using chicken 4.6.5 on
Windows 7. I suspect on a fresh install of chicken it will fail. When
installed to an existing (as of a few days ago) install of chicken it
is fine. Suggestions a
Hello Thomas,
This is a bug. I will look into it. Sorry but thank you for reporting.
Kon
On Feb 1, 2011, at 5:03 PM, Thomas Hintz wrote:
Using csi and GNU readline (I don't think I'm doing anything
wrong...):
#> (use srfi-19)
#> (date-subtract-duration (current-date) (make-duration days: 3
Using csi and GNU readline (I don't think I'm doing anything wrong...):
#> (use srfi-19)
#> (date-subtract-duration (current-date) (make-duration days: 3))
Error: (+) bad argument type - not a number: #
Call history:
def-tt304312
srfi-19-date#default-date-clock-type
Kon,
Would you update srfi-19 and srfi-29 to compile against the
experimental branch in chicken?:
http://bugs.call-cc.org/ticket/481
http://bugs.call-cc.org/ticket/482
The patch is very simple, getenv has been deprecated in favor of
get-environment-variable.
These are the only two srfi-* eg
The srfi-19 module doesn't seem to export (among others)
seconds->time, instead exposing the srfi-18 seconds->time, which for
example causes this to fail:
(seconds->time (time->seconds (current-time)))
They're available in srfi-19-time, though that seems a bit odd given
that srfi-19 already e
Sorry for the extraordinarily long-winded email the first time around.
The attached patch seems to fix the problem:
d...@kili:~/tr/scheme$ export TZ=EST5EDT
d...@kili:~/tr/scheme$ csi -q t.scm
#,(date 39200 9 4 2 13 9 2009 -14400 EDT #t #f #f #f)
Sun Sep 13 02:04:09-0400 2009
d...@kili:~/tr/sc
Hi Kon!
Under OpenBSD, I'm required to set the TZ environment variable:
d...@kili:~/tr/scheme$ csi
CHICKEN
(c)2008-2009 The Chicken Team
(c)2000-2007 Felix L. Winkelmann
Version 4.1.7
openbsd-unix-gnu-x86-64 [ 64bit manyargs dload ptables applyhook ]
compiled 2009-09-02 on kili.jsbsystems.com (O
On Sep 2, 2009, at 1:50 PM, David N Murray wrote:
On Sep 2, Christian Kellermann scribed:
find a patch for the srfi-19 egg attached to this email. When applied
to the trunk of the chicken3 egg it will happily install on chicken
4. This has been sent to Kon for review, so don't consider this o
On Sep 2, Christian Kellermann scribed:
> find a patch for the srfi-19 egg attached to this email. When applied
> to the trunk of the chicken3 egg it will happily install on chicken
> 4. This has been sent to Kon for review, so don't consider this one
> blessed by the original author. Maybe Kon wi
Hi Dave,
find a patch for the srfi-19 egg attached to this email. When applied
to the trunk of the chicken3 egg it will happily install on chicken
4. This has been sent to Kon for review, so don't consider this one
blessed by the original author. Maybe Kon will get around to commit
this soon.
Kin
Hi Dave
On Tue, 01 Sep 2009 16:02:41 -0400 (EDT) David N Murray
wrote:
> I'm a noob to Scheme & Chicken, so forgive me if this is really trivial,
> but I'm struggling mightily.
>
> # csi
> CHICKEN
> (c)2008-2009 The Chicken Team
> (c)2000-2007 Felix L. Winkelmann
> Version 4.1.0 - SVN rev. 1529
Hi all,
I'm a noob to Scheme & Chicken, so forgive me if this is really trivial,
but I'm struggling mightily.
# csi
CHICKEN
(c)2008-2009 The Chicken Team
(c)2000-2007 Felix L. Winkelmann
Version 4.1.0 - SVN rev. 15292
openbsd-unix-gnu-x86-64 [ 64bit manyargs dload ptables applyhook ]
compiled 200
On Apr 14, 2009, at 7:29 AM, Peter Bex wrote:
On Tue, Apr 14, 2009 at 07:16:37AM -0700, Kon Lovett wrote:
The '(use ...' has been inactive for some time. The setup specifies
'require-at-runtime' which is sufficient to load the components.
Please tell me more about systems where this is not tru
On Tue, Apr 14, 2009 at 07:16:37AM -0700, Kon Lovett wrote:
> The '(use ...' has been inactive for some time. The setup specifies
> 'require-at-runtime' which is sufficient to load the components.
> Please tell me more about systems where this is not true. (MacOS 10.5
> shouldn't be one of th
On Apr 14, 2009, at 1:51 AM, Peter Bex wrote:
On Tue, Apr 14, 2009 at 02:20:37AM -0500, Eduardo Cavazos wrote:
Hello,
I installed the SRFI-19 egg a little while ago on Chicken 3.4.0.
However, it seems that basic procedures like 'current-time' aren't
available:
~ # csi
CHICKEN
(c)2008 The Ch
On Tue, Apr 14, 2009 at 02:20:37AM -0500, Eduardo Cavazos wrote:
> Hello,
>
> I installed the SRFI-19 egg a little while ago on Chicken 3.4.0.
> However, it seems that basic procedures like 'current-time' aren't
> available:
>
> ~ # csi
>
> CHICKEN
> (c)2008 The Chicken Team
> (c)2000-2007 Fel
Hello,
I installed the SRFI-19 egg a little while ago on Chicken 3.4.0.
However, it seems that basic procedures like 'current-time' aren't
available:
~ # csi
CHICKEN
(c)2008 The Chicken Team
(c)2000-2007 Felix L. Winkelmann
Version 3.4.0 - linux-unix-gnu-x86 [ manyargs dload ptables app
Here is a bug report for date comparison. Thank you.
$ csi
CHICKEN
(c)2008 The Chicken Team
(c)2000-2007 Felix L. Winkelmann
Version 3.4.0 - linux-unix-gnu-x86-64 [ 64bit manyargs dload ptables
applyhook ]
SVN rev. 11987 compiled 2008-12-02 on chew-z (Linux)
#;1> (use srfi-19)
; loading /usr/
Here is a bug report for add-duration. Thank you!
(10:49:21 PM) lisppaste: acarrico pasted "add-duration" at
http://paste.lisp.org/display/71475
(11:56:58 PM) raikov: acarrico: I get the same error
(03:46:43 AM) sjamaan: acarrico: You might want to post this to the
mailinglist, or mail it direct
On Nov 7, 2008, at 12:58 PM, Timothy Beyer wrote:
At Fri, 7 Nov 2008 10:19:36 -0800,
Hi Kon,
Kon Lovett wrote:
Hello Tim,
Sorry you are having problems with the SRFI 19 Chicken impl.
On Nov 6, 2008, at 7:56 PM, Timothy Beyer wrote:
When the "srfi-19" egg loads it initializes the '(lo
At Fri, 7 Nov 2008 10:19:36 -0800,
Hi Kon,
Kon Lovett wrote:
>
> Hello Tim,
>
> Sorry you are having problems with the SRFI 19 Chicken impl.
>
> On Nov 6, 2008, at 7:56 PM, Timothy Beyer wrote:
>
> >
> > Dear Chicken Users List,
> >
> > Since approximately version 2.6 I have noticed that (curr
Hello Tim,
Sorry you are having problems with the SRFI 19 Chicken impl.
On Nov 6, 2008, at 7:56 PM, Timothy Beyer wrote:
Dear Chicken Users List,
Since approximately version 2.6 I have noticed that (current-date)
thinks that the date is 1987. These tests were performed on chicken
scheme
Dear Chicken Users List,
Since approximately version 2.6 I have noticed that (current-date) thinks that
the date is 1987. These tests were performed on chicken scheme 3.3.0, (on
FreeBSD) though I have only documented these problems on all of the 3 series.
(I am not sure when the problem began
Hello,
Thanks for reporting this. I have changed the version comparison
procedure in chicken-setup to compare versions numerically, but this
was after release 3.1.0. The issue is fixed in the development
snapshots, and the upcoming release 3.2.0.
-Ivan
Hans Bulfone <[EMAIL PROTECTED]>
hi,
when i want to install srfi-19 on a fresh chicken 3.1.0 installation
(without old eggs or something) it tells me:
Error: the required extension `srfi-29' is older than 1.5, which is
what this extension requires
but:
# chicken-setup -l | grep srfi-29
srfi-29Ve
On 9/3/07, Shawn Rutledge <[EMAIL PROTECTED]> wrote:
> On 9/3/07, John Cowan <[EMAIL PROTECTED]> wrote:
> > So go with the flonums; they're simpler.
>
> If I take that approach maybe it makes more sense to use srfi-18 time
> objects. They consist of only a single flonum, right? rather than
>From
On 9/3/07, John Cowan <[EMAIL PROTECTED]> wrote:
> So go with the flonums; they're simpler.
If I take that approach maybe it makes more sense to use srfi-18 time
objects. They consist of only a single flonum, right? rather than
seconds (which ought to have been a fixnum but instead must be a
rou
On 9/3/07, Shawn Rutledge <[EMAIL PROTECTED]> wrote:
>
> It would be nice if there were a way to keep 32-bit numbers that have
> been received from C, store them that way inside the time object, pass
> them across s11n that way, and only convert to bignum when you call
> (time-second).
You could p
AFAIK s11n does not take into account different byte-ordering which is
likely to be an issue if you are communicating across different hardware.
Cheers,
John.
Shawn Rutledge wrote:
I'm looking into ways for Scheme processes to communicate with each
other. s11n caught my eye. It's pretty coo
On 9/3/07, John Cowan <[EMAIL PROTECTED]> wrote:
> Shawn Rutledge scripsit:
>
> > Unix timestamps are annoying in Scheme because nowadays they take up
> > most of a 32-bit unsigned int, so it won't fit in a fixnum. If I want
> > to pass a timeval from a C function to Scheme, I see that the
> > uns
Shawn Rutledge scripsit:
> Unix timestamps are annoying in Scheme because nowadays they take up
> most of a 32-bit unsigned int, so it won't fit in a fixnum. If I want
> to pass a timeval from a C function to Scheme, I see that the
> unsigned-integer32 datatype gets converted to a flonum by defau
I'm looking into ways for Scheme processes to communicate with each
other. s11n caught my eye. It's pretty cool in general. One of the
first things I'm trying to write is a daemon which handles input from
/dev/input/* and provides events to another process which connects.
For the first version I
On 5/19/07, Dan Muresan <[EMAIL PROTECTED]> wrote:
Well, I was in a rush, so I've wrapped strftime(). This might actually
be useful to others, so I'm posting it. I've used SWIG, but I'm sure
it's trivial using the Chicken FFI (which I don't know though):
You could do it like this, though it pro
Chicken 2.6 has inconsistent meaning for timezone offset across
platforms. 2.61 fixed this.
Provided you are not using MacOS X or Windows you can get the current
version (2.6.9) which skips the requirement otherwise.
Well, I was in a rush, so I've wrapped strftime(). This might actually
be u
On May 19, 2007, at 5:18 PM, Dan Muresan wrote:
Hi all,
the latest stable release (Chicken 2.6) doesn't work with the
srfi-19 egg. Sorry if I missed any related messages (I don't think
I did) but it sounds like a bad idea for an egg do depend on the
unstable version of Chicken... Or mayb
Hi all,
the latest stable release (Chicken 2.6) doesn't work with the srfi-19
egg. Sorry if I missed any related messages (I don't think I did) but it
sounds like a bad idea for an egg do depend on the unstable version of
Chicken... Or maybe a new release is imminent?
# chicken-setup srfi-19
On Mar 28, 2007, at 2:47 PM, Hans Bulfone wrote:
hi,
but i still get the wrong result without TZ. i think this is because
seconds->local-time also returns the offset in seconds west of UTC.
i must admit, i'm rather surprised about those different tz offset
interpretations :) until yesterd
hi,
On Tue, Mar 27, 2007 at 06:28:28PM -0700, Kon Lovett wrote:
> Yes. The TZ env-var is parsed properly by the locale egg but the tz-
> offset was used incorrectly by my srfi-19 code. (Well, I did have my
> locale documentation wrong. Said the opposite of what is true.)
>
> 2.6.3 will be avai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 27, 2007, at 2:57 PM, Hans Bulfone wrote:
np, thanks for the quick fix!
but i still get the wrong time:
#;7> (values (current-date) (current-date (local-timezone-locale))
(current-date 7200))
#,(date 403000116 9 36 21 27 3 2007 0 UTC
hi,
On Mon, Mar 26, 2007 at 11:21:29PM -0700, Kon Lovett wrote:
> Please get the new locale (0.3) & srfi-19 (2.6.2) eggs.
>
> With TZ=CEST2:00 (incorrect but enough to test)
>
> #;2> (values (current-date) (current-date (local-timezone-locale))
> (current-date 7200))
> #,(date 52274 10 15
On 3/27/07, Kon Lovett <[EMAIL PROTECTED]> wrote:
Please get the new locale (0.3) & srfi-19 (2.6.2) eggs.
With TZ=CEST2:00 (incorrect but enough to test)
#;2> (values (current-date) (current-date (local-timezone-locale))
(current-date 7200))
#,(date 52274 10 15 6 27 3 2007 0 UTC #f 2 86)
#
On Mar 26, 2007, at 2:25 PM, Hans Bulfone wrote:
hi,
i'm having some timezone-related problems with srfi-19:
it is now:
[EMAIL PROTECTED]:~$ LC_ALL=C date
Mon Mar 26 23:07:16 CEST 2007
CEST = central european summer time = UTC + 2 hours
#;37> (values (current-date) (current-date (local-time
hi,
i'm having some timezone-related problems with srfi-19:
it is now:
[EMAIL PROTECTED]:~$ LC_ALL=C date
Mon Mar 26 23:07:16 CEST 2007
CEST = central european summer time = UTC + 2 hours
#;37> (values (current-date) (current-date (local-timezone-locale))
(current-date 7200))
#,(date 1773119
Hi Felix,
("My" srfi-19 is based/inspired on/by the PLT Scheme & Scsh ports of
the reference, but I didn't do anything extraordinary to chg your
"crap" opinion. I do try to clean & streamline where I can though.)
Nearly "finished" w/ locale, srfi-29 & srfi-19. They pass their
tests. Some
47 matches
Mail list logo
