[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFC: enum instead of #define for tokens

From: Hans Aberg
Subject: Re: RFC: enum instead of #define for tokens
Date: Fri, 5 Apr 2002 16:59:18 +0200

At 02:37 -0800 2002/04/05, Paul Eggert wrote:
>I wasn't so much worried about people using yytranslate in their own
>code (they deserve what they get; it's private).  I was worried about
>how 'bison' would output a yytranslate that will work on an EBCDIC
>host, even when 'bison' itself is running on an ASCII host.  This
>issue is independent of the pointer-versus-int issue.

Is this cross compiler problem common?

-- Note that the problem does not exist for Unicode UTF-n encodings, n >=
21, as those are the same on all platforms.

If one really needs to have your feature, there are two solutions: "Akim",
i.e., do not use the Bison char feature. Or having normally unsorted tables
with entries of the form
  { 'a', n }
Then this file will properly translated.

Note that one may want to use the yytranslate[] table as is if one is using
distributed programming, say a WWW-browser reading ASCII on an EBCDIC

  Hans Aberg

reply via email to

[Prev in Thread] Current Thread [Next in Thread]