Alex Shinn

What exactly is it complaining about? Different architectures will have different build options, with different sets of features - this is intentional.

That's annoying. It says "if present," can we just omit them altogether? If not, how hard is it to just create separate arch files for the 32-bit archs? I think...

The best thing for users is exactly what Chibi already does. There are documented macros in features.h which control both the declaration and definition of the optional symbols. Trying to...

This isn't a matter of stability between releases. The problem described by #719 is features not supported on certain architectures confusing some Debian packaging feature I'm not familiar with. ABI...

@barak, there is no problem regarding changing features in Debian. They don't change - we always use the default build, and the default build is stable. If you want a...

The default features would not change in such a way as to break ABI compatibility.

Regarding breaking strict aliasing, it's a bit tedious to implement that properly. I'd wait for a complaint from an actual SPARC user before worrying about it :)

For general questions, please ask on the mailing list: [email protected] Chibi searches the same module load path for shared libraries as for Scheme code. You can use `add-module-directory' from Scheme...

Yes, this is a known limitation... I thought it was documented somewhere. Although looking at sexp_char_ready_p now I see nothing preventing us checking for a full char...

Did this arise from a real-world program? I'm not a fan of `char-ready?` in general. If it errs towards `#f`, then a program waiting for a character to be ready...