Re:Re: [thread] barrier.cpp don't compile with msvc60 & stlport]
cool - i use the same configuration! So every has to work ;-))
Why does it compiles on meta-comm and not on my machine? I tried it on two differend machines. (but both with the same stlport)
So what's different?
I use the ms-iostream - what kind of iostreams is the regressiontest using?
I use msvc + stlport 4.5.3 compiled with streams and it builds the serialization library on my machine w/o problems. The daily tests show what seems to be a similar configuration which fails to build with a compile error in spirit. Sooo one or more of the following is true a) something is different - its not clear what b) spirit 1.6 - needs some sort of tweak - I'm not sure this will ever happen. c) Its really annoying to see a column of all failures knowing that the issue is fixable but not by me. Robert Ramey
Robert Ramey wrote:
I use msvc + stlport 4.5.3 compiled with streams and it builds the serialization library on my machine w/o problems. The daily tests show what seems to be a similar configuration which fails to build with a compile error in spirit. Sooo one or more of the following is true
a) something is different - its not clear what b) spirit 1.6 - needs some sort of tweak - I'm not sure this will ever happen.
It's happening now. Just inform me and I'll gladly tweak what needs to be tweaked. Just holler and I'll be glad to be of service. It's just so easy to miss and more compilers are being added all the time. Aleksey, if it's not too much too ask, would it make sense if Spirit 1.6 be added to the developer report? There is only a limited set of compiler/configurartions that I can test and it would be a great help if I can see the results on more compilers. Thoughts? General question: until *when* will we have to support old compilers such as borland, VC6/7 and g++2.95.3 ??? Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net
Joel de Guzman writes:
Aleksey, if it's not too much too ask, would it make sense if Spirit 1.6 be added to the developer report?
I'm afraid neither I nor Misha have resources to look into it at the moment.
There is only a limited set of compiler/configurartions that I can test and it would be a great help if I can see the results on more compilers. Thoughts?
Is there any reason to use Spirit 1.6 instead of 1.8 besides when you have to work with old MSVC/Borland? If not, and if those configurations are being tested, it's an acceptable compromise, IMO.
General question: until *when* will we have to support old compilers such as borland, VC6/7 and g++2.95.3 ???
Here's how I see it: Individual library authors can drop the support of any particular compiler at their will. If there are other libraries that depend on it, and their developers want to continue to support the dropped compiler, they can negotiate the conditions on which it's going to happen. It's totally up to the interested parties what the result of this negotiation is going to be. -- Aleksey Gurtovoy MetaCommunications Engineering
participants (3)
-
Aleksey Gurtovoy -
Joel de Guzman -
Robert Ramey