Neil Jerram <[EMAIL PROTECTED]> writes: >> Also (and don't try this at home kids): >> (define 'x (* x x)) >> '2 >> => 4 > > And presumably (or in my view) this is all fine, except for the last > example, where Guile should signal an error or at least give a > warning. Right?
Hmm. There are two things here that might want a warning: redefining something that was a macro as a variable; and shadowing a core definition. We we already warn when importing something that shadows a core definition, so we could as well warn when redefining one. Opinions? -- GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405 _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://lists.gnu.org/mailman/listinfo/guile-user
