A quick thank you to everyone who responded. Those tips helped
immensely. When starting out with a new system, not only does one need
questions answered, you need to know what questions to ask! I'd like
to *think* I'm on better ground for both of those items.
Cheers,
-M
Hello Chicken expertgenzia,
In attempt to broaden my knowledge of Chicken, I'm attempting to
create an egg for the GEOS C library[1]. My first cut has been to use
easyffi, and I'm pleased with the results. With minimal hacking at the
GEOS API header[2] I've been able to see some results.
Mark Fredrickson scripsit:
1. Many of the GEOS functions return 'char', even though the actual
data should be a bool. Is there a way to tell easyffi to treat these
characters as #t/#f? I'm thinking there might be a __declare() for it,
but I didn't see anything that made immediate sense
On Jan 10, 2008 10:17 PM, Mark Fredrickson [EMAIL PROTECTED] wrote:
1. Many of the GEOS functions return 'char', even though the actual
data should be a bool. Is there a way to tell easyffi to treat these
characters as #t/#f? I'm thinking there might be a __declare() for it,
but I didn't see
