Aleksey Gurtovoy wrote:

Russell Hind writes:

...

Because bcc32 can't deal with spirit-1.8, to use spirit and boost 1.31, I've replaced spirit.hpp and the spirit directory in boost with the 1.6 distribution.

This doesn't work with the latest boost code, it looks like the errors are due to the changes mpl that were mentioned.

Are there any plans to update spirit 1.6 to work with latest boost so those of us with older compilers can use the two together?

Russell,

SPIRIT_1_6 branch in Boost CVS contains the latest version of, well, Spirit 1.6 that is compatible with the rest of the latest Boost, including MPL.

Thank you very much, Aleksey! And thank you too for fixing all apply_if's and stuff in all spirit related libraries in the boost CVS. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net

Russell Hind wrote:

I mentioned this ages ago but just hit the issue again:

I've got the SPIRIT_1_6 branch out and have a compile problem with BCB6.

in spirit\pheonixz\closures.hpp line 237:

impl::closure_frame_holder<closure_frame>& frame;

BCB6 throws an error on this. Changing it to

impl::closure_frame_holder<closure_frame<ClosureT> >& frame;

solves the error for me. Not sure if it will affect other compilers though

Done. I'd appreciate if you can also provide more workarounds for borland. I seldom use the compiler now. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net

Russell Hind wrote:

Joel wrote:

...

Done. I'd appreciate if you can also provide more workarounds for borland. I seldom use the compiler now.

This is the only problem I've hit so far. I only use spirit for a very simple XML parser so the usage is limited.

At the very least, I notice compiler warnings. No? Fixing those warnings would be a good first step.

As and when I come accross problems I'll do my best to fix them, but my support may be limited.

Any help is highly appreciated. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net

Russell Hind wrote:

Joel wrote:

...

At the very least, I notice compiler warnings. No? Fixing those warnings would be a good first step.

I don't get any warnings, but as mentioned, the code I'm using is very simple. I also have certain warnings disabled (but only some strange iterator related ones I think)

Is there any code you can post that you have trouble with and I can try? (I've not looked in to running the tests yet, and don't really have time at the moment).

No worries. Whenever you have some time to peek into the tests will be fine. Many thanks, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net