On 5/10/07, Mark Voortman [EMAIL PROTECTED] wrote:
2. Have you considered the GC implications?
There should be no garbage collection. I just load it into memory once and
that's it.
Since chicken uses a (generational) stop-and-copy collector, all data
allocated will be moved from one space
On 5/10/07, Alex Queiroz [EMAIL PROTECTED] wrote:
Hallo,
I've got to bind one of the following functions:
handle* Hbox(Ihandle *child, ...);
handle* Hboxv(Ihandle **children);
Which one is easier in Chicken? I guess I'll have to create a list
using the C API, right?
The former:
(use
On 5/11/07, felix winkelmann [EMAIL PROTECTED] wrote:
On 5/10/07, Mark Voortman [EMAIL PROTECTED] wrote:
2. Have you considered the GC implications?
There should be no garbage collection. I just load it into memory once and
that's it.
Since chicken uses a (generational) stop-and-copy
Hallo,
On 5/11/07, felix winkelmann [EMAIL PROTECTED] wrote:
But if you want more type-safety, or a general Scheme-interface (not just
use HBox in some code), then you should indeed consider creating a
pointer list in C, or converting a Scheme list to such a pointer list).
Thanks for all
Hi folks,
Sorry for the maybe stupid question: is the following expression
supposed to return #f on Windows?
(file-exists? .\\)
(file-exists? (current-directory)) returns the path to the current
directory.
Under Unix[-like] systems, (file-exists? ./) returns the path to the
current
