-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/2013 11:22 PM, Felix wrote:
This usually means an inconsistent heap: some random data is interpreted as
a proper Scheme object and the header contains some huge size indicator.
I wonder if it might be possible to come up with some sort
On Thu, Jan 31, 2013 at 09:14:32AM +, Alaric Snell-Pym wrote:
On 01/31/2013 01:06 AM, Hugo Arregui wrote:
That's right, in fact, when I started the project I think to do so,
just create the bindings, but, to be honest, I think it will more fun
if I do it from scratch.
In general, I
Hey Felix,
thanks a lot for your ideas! I checked the channel code and found that
neither it nor one of its dependencies uses the FFI. The dependencies
are data-structures, extras, lolevel, srfi-1, srfi-18, srfi-69, and
miscmacros. Maybe some of the core units do use some FFI calls, I have
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/31/2013 12:34 PM, Moritz Heidkamp wrote:
What I need now is someone encouraging me in such an effort,
suggesting various improvements to that work-intensive and toilsome
project and who offers reliable support and hacking time. To remain
FYI, the docs for endian-blob don't indicate the ordering of the endian blob
after type-endian_blob. From reading the code it's MSB and there's an
optional mode arg to these procedures. Should this be documented? Similarly
the optional mode argument to byte-blob-endian-blob is documented as
I think you are right Jim,
This is the way that C implementation packs float/doubles:
https://github.com/msgpack/msgpack-c/blob/master/pack_template.h#L635
Regards,
Hugo
___
Chicken-users mailing list
Chicken-users@nongnu.org
Hi all,
I also have been encountering some mysterious heap full errors and even
segmentation faults when working with large data sets and some tree data
structures or srfi-4 vectors. For example, the attached code does not
include any FFI stuff, yet it causes segmentation faults when compiled
You are right, I have updated the endian-blob documentation accordingly.
Thanks,
Ivan
On Fri, Feb 1, 2013 at 8:16 AM, Jim Ursetto zbignie...@gmail.com wrote:
FYI, the docs for endian-blob don't indicate the ordering of the endian
blob after type-endian_blob. From reading the code it's
Attached is an even simpler test case that causes segmentation fault even
when compiled with -O -d2 options but works fine when run under the
interpreter.
On Fri, Feb 1, 2013 at 10:02 AM, Ivan Raikov ivan.g.rai...@gmail.comwrote:
Hi all,
I also have been encountering some mysterious
On Jan 28, 2013, at 2:53 PM, Hugo Arregui wrote:
3) To read/write float/double numbers (in ieee754) i'm using
endian-blob egg (here[4]), it's there any alternative without
implementing the full float/double-binary logic (which seems quite
complicated)?
Maybe I'm overlooking something, but
10 matches
Mail list logo
