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
CHARCON
imcc/docs/syntax.pod has the following:
=item 'char constant'
Are delimited by B<'>. They are taken to be C encoded. No escape
sequences are processed.
But in fact B<'> behaves like B<"> without escapes or encoding/charset
prefixes:
[EMAIL PROTECTED]> cat foo.
