|
From: | Tobia Conforto |
Subject: | Re: [Chicken-users] ditching syntax-case modules for the utf8 egg |
Date: | Fri, 14 Mar 2008 12:41:51 +0100 |
Alex Shinn wrote:
I'm considering changing the utf8 egg to no longer use syntax-case modules, so that it would work like the numbers egg.The way this would work is that, naturally, if you wanted to use utf8 semantics you'd just (use utf8), this time with no need for syntax-case and nothing to import.External modules, by default, would integrate standard string procedures and not be affected. However, if you wanted to make an extension optionally work with utf8 semantics you could compile it with (declare (not usual-integrations))
This seems very straightforward and natural. What are the disadvantages, if any? (except for compatibility, aka. tremendous breakage as Felix put it)
I mean, what does the syntax-case module system gives us with regard to the utf8 egg that the proposed, numbers-like system wouldn't allow? Why was it done like that in the first place?
Tobia
[Prev in Thread] | Current Thread | [Next in Thread] |