Bob Rogers wrote:
A syntax for specifying multiple characters without escapes seems like a
useful thing, a la Perl5, but being unable to specify an encoding or
charset seems less useful, even for a single character.
This is probably rather simply to fix: attach the same lexer rules to
CHARCONSTANT as done with STRINGCONSTANT and the verify and create a
string with the given encoding and charset.
... In fact, I was
expecting a single character to be represented as an integer internally,
or at least to be easily converted to one, so I was surprised that this
didn't print "120\n":
[EMAIL PROTECTED]> cat bar.pir
.sub _main @MAIN
I1 = 'x'
This is also not a big deal, mk_const() or such can handle this.
leo
