Re: [boost] Spirit V1.8 to V2.1 Porting Errors

Subject: Re: [boost] Spirit V1.8 to V2.1 Porting Errors
From: Alireza Bemanian (bemanian_at_[hidden])
Date: 2010-02-25 13:45:04

Beside four additional deprecated warnings, the errors remain the same if
the includes and namespaces were switched back to original. The version of
spirit used earlier is 1.8.x written at the top of the version.h file within
the spirit directory. 

The other changes made to the code during the port are, now the boost
directory is used by its entirety outside the project directory, and not
only the Spirit part within the project directory. Apparently all the set
additional include paths for the change seem to work fine. The other change
is switch from the VS2008 to VS2010 RC1. The code builds when the older
version of the spirit is used as before, although the parsing works
partially and apparently not for the entire existing grammar structure. This
is the reason that I decided to switch to the new Spirit version at the same
time too.

Regards,
Reza Bemanian

-----Original Message-----
From: boost-bounces_at_[hidden] [mailto:boost-bounces_at_[hidden]]
On Behalf Of Hartmut Kaiser
Sent: Thursday, February 25, 2010 11:54 AM
To: boost_at_[hidden]
Subject: Re: [boost] Spirit V1.8 to V2.1 Porting Errors

> Yes, these are the compilation errors.
> 
> 2>------ Build started: Project: Project, Configuration: Debug Win32 --
> ----
[snipped errors]

> I tried to use the Spirit Classic by changing the project include and
> namespace statements to classic. Those are the only changes made to the
> project for the port. The library is stored as the complete download
> with
> the rest of the boost libraries including the smart pointer, and have
> not
> further tried to compile the code with removing such directories.

Ok, I have to take your word for it. But how do you think I should know what
actually happens in your code if all what you're showing to me is a listing
of completely unrelated (to Spirit) error messages? I have no crystal ball
to see what you're doing. So I must ask you again, please provide me with a
small self contained piece of code reproducing your problem.

Does your code compile if you do not change the Spirit #include's (yes I
know you'll see the deprecated warnings then)? 
What Boost versions have your code been compiled with before your changes?

Regards Hartmut

---------------
Meet me at BoostCon
www.boostcon.com

_______________________________________________
Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost