Hi, Hartmut, I did as what you told me, and it fixed the problem. Thank you so much! regards, Fanzhe Cui -----Original Message----- From: Hartmut Kaiser [mailto:hartmut.kaiser@gmail.com] Sent: Wednesday, July 04, 2007 7:21 AM To: 'Fanzhe Cui'; 'Spirit General Mailing List' Subject: RE: Problem with wave in boost 1_34_0 Fanz,
I had a program using wave in boost_33_1 that worked perfect. It used wave library as a preprocessor to a script parser, and it worked with boost_33_1. But when I was trying to compile it with wave in boost 1_34_0, I got error. I think it might be a known problem to you guys and you might know the solution to the problem.
The program code that give error was: lexer_type it = lexer_type(instr.begin(), instr.end(), pos, boost::wave::language_support( boost::wave::support_cpp|boost::wave::support_long_long));
And the error was:
C2039: 'support_long_long' : is not a member of 'boost::wave' 1>c:\users\diamond\src\scriptpreproc.cpp(80) : error C2065: 'support_long_long' : undeclared identifier 1>c:\users\diamond\src\scriptpreproc.cpp(80) : error C2514: 'boost::wave::language_support' : class has no constructors 1> c:\users\tools\boost\boost_1_34_0\boost\wave\language_support. hpp(25) : see declaration of 'boost::wave::language_support' 1>c:\users\diamond\src\scriptpreproc.cpp(80) : error C2661: 'boost::wave::cpplexer::lex_iterator<TokenT>::lex_iterator' : no overloaded function takes 4 arguments
Can you please point me to the right direction or give me a tip to resolve this problem?
Doh! I was not aware of this interface breaking change in Wave (for this reason its not documented anywhere). As I now remember I unified the naming of the options and flags, so that the option you're using is now named: 'support_option_long_long'. If you change your code accordingly, it should compile again. For your reference: please have a look at the file boost/wave/language_support.hpp, where all related options are defined. Sorry for the trouble, I should have documented this. Regards Hartmut