On Jan 29, 2008 3:22 PM, Graham Fawcett [EMAIL PROTECTED] wrote:
On Jan 29, 2008 3:21 PM, Hans Bulfone [EMAIL PROTECTED] wrote:
Yeah, that's a ugly error message. But what would it mean to read an
arbitrary-length string from a network port?
it's not supposed to read an arbitrary-length
hi,
On Tue, Jan 29, 2008 at 12:22:04PM -0800, Kon Lovett wrote:
Fixed in trunk/chicken.
thanks, kon!
bye,
hans.
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
On Jan 29, 2008, at 12:21 PM, Hans Bulfone wrote:
snip
probably the latter as ##sys#custom-input-port's implementation
of read-string! (in posixunix.scm) doesn't seem to check for #f
either.
Fixed in trunk/chicken.
btw. this is with chicken 2.732 but after a quick check i think it's
the
Hi Hans,
On Jan 28, 2008 7:38 PM, Hans Bulfone [EMAIL PROTECTED] wrote:
on my system (linux-amd64) when i use read-u8vector! to read from a
port created by tcp-accept or tcp-connect and give #f as LENGTH, i get
the unrealistic error:
out of memory - heap full while resizing - execution
hi,
on my system (linux-amd64) when i use read-u8vector! to read from a
port created by tcp-accept or tcp-connect and give #f as LENGTH, i get
the unrealistic error:
out of memory - heap full while resizing - execution terminated
when i use the length of the vector as LENGTH it works as
