Custom Query (1630 matches)

$ cat foo
#!/usr/bin/csi -s

(print 'foo)

$ cat foo.scm
#!/usr/bin/csi -s

(print 'foo.scm)

$ ./foo
foo.scm

$ csi
CHICKEN
(c)2008-2009 The Chicken Team
(c)2000-2007 Felix L. Winkelmann
Version 4.1.0 - SVN rev. 15292
linux-unix-gnu-x86 [ manyargs dload ptables applyhook ]
compiled 2009-08-03 on nachos (Linux)

#;1> (load "foo")
; loading foo.scm ...
foo.scm
#;2>

Should foo.scm be loaded when foo exists (specially when executed as a script)?

Building an extension may need to load extensions/.so's that have just been produced by the current installation process, but require'ing extensions will always look in the repository first (and possibly load an obsolete version, if the extension has been installed at an earlier point).

We should provide an option (csc + chicken) that forces the search/load order to look in the current directory first. Note that the correct order for normal use should stay repo-first, then current directory, or random files in the current directory may break applications. chicken-install should invoke csc with the extra option.

(< 1237940039285380274899124223 1237940039285380274899124224.0) ;=> #t

but

(< 1237940039285380274899124224.0 1237940039285380274899124225) ;=> #f

This is caused by using the flonum domain for all comparisons involving bignums.

(exact->inexact 1237940039285380274899124225) ;=> 1237940039285380274899124224.0