Sounds good. The complete specification for the linux boxes I have tested this on is
RHEL 3 fully updated on an intel Xeon with g++ 3.4.3
Ubuntu Breezy Badger fully updated on an intel pentium M with g++ 4.0.3
On both machines I tested both the 1.33.1 release and the CVS version. 
I appreciate all your help in tracking down this issue.

Thanks
Andreas

On 4/22/06, Hartmut Kaiser < hartmut.kaiser@gmail.com> wrote:

Andreas Sæbjørnsen wrote:

> I do not know why you were not able to reproduce the error as
> I reproduced it on two different machines using two different
> boost installations. Using the attached source-file you
> should be able to reproduce the error. Both icc and g++
> compiles this file without error.
>
> If the behaviour in section 2.2.2 of the standard lead to
> Wave being unable to preprocess some C++ source-files that
> cpp and the EDG preprocessor will accept, what do you think
> about creating a feature for optionally turning this behaviour off?

I've induced a null byte into your sample and gcc complains about it as
well. So my guess is, that something else goes wrong. But since I still have
no luck in reproducing your original problem here on my Windows machine I'll
have to try it on a linux box, but will have the possibility for that next
week only.

Regards Hartmut

>
> Regards
> Andreas
>
>
>
>
> On 4/21/06, Hartmut Kaiser < hartmut.kaiser@gmail.com
> <mailto:hartmut.kaiser@gmail.com> > wrote:
>
>
>       Andreas Sæbjørnsen wrote:
>
>       > Using the wave driver reference implementation on the
> code found at:
>       >       http://folk.uio.no/andsebjo/bugInducingCode.C
> < http://folk.uio.no/andsebjo/bugInducingCode.C>
>       > I get the following error:
>       >       bugInducingCode.C(10157): error: generic lexing error:
>       > '\000' in input stream This code compiles with g++ and if any
>       > line is cut within the file it does not fail with Wave.
>       > The code contains only C++ syntax so it is basically a test
>       > of the cpplexer.
>       > Is this a know problem?
>       >
>       > This problem occurs in both my two months old CVS version of
>       > boost and the 1.3.1 build.
>
>       Hmmm. Sorry I'm not able to reproduce this problem
> here. But the error you
>       get says your input stream contains a binary 0 (zero)
> byte. And yes it's a
>       lexer diagnostic.
>
>       The standard says ( 2.2.2 [lex.charset]):
>
>       <quote>
>       If the hexadecimal value for a universal character name
> is less than 0x20 or
>       in the range 0x7F0x9F (inclusive), or if the universal
> character name
>       designates a character in the basic source character
> set, then the program
>       is illformed.
>       </quote>
>
>       So I'm pretty sure Wave is right to diagnose this.
>
>       Could you send me the file as an attachment, please,
> just to make sure I
>       really get it as you have it on your disk.
>
>       Regards Hartmut
>
>
>       _______________________________________________
>       Boost-users mailing list
>       Boost-users@lists.boost.org
> <mailto:Boost-users@lists.boost.org >
>       http://lists.boost.org/mailman/listinfo.cgi/boost-users
> < http://lists.boost.org/mailman/listinfo.cgi/boost-users>
>
>
>
>

_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users