Hi all.
Is there a recommended way to declare some large expressions (> 100 MB)
in a compiled program as read-only and more importantly
as not gc-able (the garbage collector should be saved from traversing
these large structures again and again)?
Should the constant value be compiled in or should
On Sun, Jan 05, 2014 at 06:07:33PM +0100, Sven Hartrumpf wrote:
> Hi all.
>
> Is there a recommended way to declare some large expressions (> 100 MB)
> in a compiled program as read-only and more importantly
> as not gc-able (the garbage collector should be saved from traversing
> these large stru
All,
Please find below the call for papers for the 3rd International Workshop on
Trends In Functional Programming in Education, TFPIE 2014. Apologies in
advance for multiple copies you may receive.
Best regards,
James Caldwell
Call for Papers
__
I'll bet if you define a 100MB literal, the resulting C file would be at least
a gigabyte and neither CHICKEN nor gcc would be able to handle it. You could
try it and let us know.
You could evict it theoretically, but for something that big, you may have to
create your own data structure in C
On Jan 5, 2014, at 11:48, Peter Bex wrote:
> Perhaps you can use object-evict!, but
>>
> that means it won't ever be reclaimed by the GC. I haven't used
> this myself yet, so I don't know if there's a way to "un-evict" the
> object when it can be GC'ed.
>
http://api.call-cc.org/doc/lolevel/ob
Not sure why this message got truncated, but it was in reference to moving an
object back into the heap, in other words unevicting it.
Felix says object-evict! is considered harmful, so keep that in mind. (It
works fine in the limited context I have used it.)
On Jan 5, 2014, at 15:27, Jim Urse
My new PC runs Windows 8.1 Pro and comes with "Hyper-V"
virtualization "built-in". Getting CHICKEN running on FBSD as a
guest OS was pretty easy, but one problem showed up.
Near the end of the test suite, 'gmake check' failed (during the
"deployment test") with the error:
'clang' 'rev-app.o'
The following produces a correct type error:
$ csi -n
#;1> (append "foo" "bar" '())
Error: (append bad argument type - not a proper list: "foo")
Whereas this does not:
$ csi -n
#;1> (use srfi-1)
#;2> (append! "foo" "bar" '())
()
I would expect to see the error in example 1 repeate
