>>>> "Hrvoje" == Hrvoje Niksic
<hniksic(a)arsdigita.com> writes:
> You need to teach the Lisp reader that the construct
> ?\033$BC8\033(B is not an error,
Hrvoje> That might go under "recognize when it cannot do so".
And then what? You're not allowed to stop, you have to do something
even though you know you're broken.
Trying to define currently erroneous behavior as correct without
turning no-mule XEmacs into Mule is a difficult design problem. We
can see the ?\302\040 problem now. I see no reason to suppose that
whatever decision we make to resolve it won't introduce more subtle
bugs. I can't see that far. Can you?
This is the same design process that produced the Mule you love to
hate so. Let's "Just Say No" to that.
> It's _much_ easier to make Mule fast, robust, and universal,
> IMHO.
Hrvoje> I wouldn't bet on it.
OK, so I was exaggerating. They're both intractable problems.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."