Re: [Chicken-users] FFI and stack use

2009-07-22 Thread Francisco Rafael Leon
John Cowan co...@ccil.org writes: In fact, it's unpredictable how much C stack you have, because each compiled Scheme function invokes its successor, leaving garbage return addresses, saved registers, etc. on the C stack. So just before calling a function that allocates lots of C stack, call

Re: [Chicken-users] FFI and stack use

2009-07-22 Thread Thomas Bushnell BSG
On Tue, 2009-07-21 at 23:37 -0400, John Cowan wrote: In fact, it's unpredictable how much C stack you have, because each compiled Scheme function invokes its successor, leaving garbage return addresses, saved registers, etc. on the C stack. So just before calling a function that allocates

Re: [Chicken-users] FFI and stack use

2009-07-22 Thread John Cowan
Thomas Bushnell BSG scripsit: But this doesn't seem right. Let's suppose the kernel stack limit is 16MB, and the Chicken Scheme stack size is set to its default of 64K. Then when my function is invoked, the kernel is still willing to expand the stack up to 15 MB. So there isn't a serious

Re: [Chicken-users] Re: Problems installing eggs

2009-07-22 Thread Jim Ursetto
Regarding objc, it's in the repository but incomplete. Regarding MacPorts, if you *always* want to look in a nonstandard location for libraries, you should be able to add /opt/local/lib and /opt/local/include to the gcc/ld flags when you compile Chicken. Easiest way to do this is probably to edit