Dave Thomas <Dave / thomases.com> writes:

> Guy Decoux suggested changing DEFAULT_KCODE, but a
> quick grep suggests it's only used in the re.c module.

But the re module is used to validate identifiers, and setting
DEFAULT_KCODE=none now makes the following fail to compile:

   = 1
 >
   /tc/dave/play/line.rb:1: Invalid char 'ৠin expression
   /tc/dave/play/line.rb:1: parse error
   = 1


So the problem is fixed (thanks, Guy!)

I'm wondering if configure.in needs to be changed to pick a default
for DEFAULT_KCODE somehow based on the machine's environment.

As a secondary issue, what does all this mean for the portability of
Ruby source. If your system is compilers with EUC and mine with NONE,
will I not be able to compile your programs?

Regards (and thanks again)

Dave


-- 
Thomas Consulting.
Innovative and successful developments with Unix, Java, C, and C++. 

Now in bookstores:
 The Pragmatic Programmer.  www.pragmaticprogrammer.com/ppbook/