On Tue, Aug 16, 2011 at 7:17 PM, David Kastrup <d...@gnu.org> wrote: >> (and I am speaking as a GUILE developer here as well) > > So what does relying on undefined behavior buy us apart from the > inability to debug type errors?
It buys us time to work on more interesting and more valuable improvements. Speaking as a long-time lilypond developer, it is my experience that the errors you point out are not a problem (except for the SCM => bool conversion). GUILE's API uses data that can be passed into C functions efficiently as parameters. This means that the SCM type must be a machine word, so the genericity suggested by the GUILE docs are a joke. If you feel compelled to change large swaths of source code by substituting x == SCM_EOL with scm_is_eq(x, SCM_EOL), then I can't stop you, but to me it just looks like a waste of time. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
