home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!cs.utexas.edu!zaphod.mps.ohio-state.edu!darwin.sura.net!jvnc.net!yale.edu!ira.uka.de!ira.uka.de!smurf.sub.org!nadia!ncc1701.stgt.sub.org!ncc1701!space
- From: space@ncc1701.stgt.sub.org (Lars Soltau)
- Newsgroups: comp.unix.questions
- Subject: Re: what does 8-bit clean mean ?
- Date: 18 Nov 92 09:30:01 GMT
- Organization: United Federation of Planets
- Lines: 28
- Distribution: world
- Message-ID: <SPACE.92Nov18113002@ncc1701.stgt.sub.org>
- References: <1e8u74INNc75@function.mps.ohio-state.edu>
- NNTP-Posting-Host: ncc1701.stgt.sub.org
- Content-Type: text/plain; charset=iso-8859-1
- Content-Transfer-Encoding: 8bit
- In-reply-to: ren@function.mps.ohio-state.edu's message of 16 Nov 1992 14:53:08 -0500
-
- >>>>> On 16 Nov 1992 14:53:08 -0500,
- ren@function.mps.ohio-state.edu (Liming Ren) said:
-
- > Somewhere I read that the C-compiler cc is not 8-bit clean. I am not sure
- > what It means?
-
- It means that the C compiler can't handle 8bit identifiers, e.g.
- NasenbΣr (you might see the Σ on the left as v or \344, depending on
- your configuration). Most C compilers can handle 8bit characters in
- strings and comments, though.
-
- > Also from the manpage of lex in UNIX, it says:
-
- > The lex command is not changed to support 8-bit symbol
- > names, as this would produce lex source code that is not
- > portable between systems.
-
- > Does this mean that lex can only be used for lexical analysis of text
- > of ascii code 0-127?
-
- I don't know about lex, but flex has an option for exactly that, i.e.
- producing an 8bit scanner. The comment above only refers to identifiers,
- not the input text.
- --
- Lars Soltau bang: <insert ridiculously long path> BIX: -- no bucks --
- smart: space@ncc1701.stgt.sub.org
-
- Will kein Gott auf Erden sein, sind wir selber Goetter.
-