Rene Rivera schrieb:
On 11/19/2010 7:38 AM, Eric Niebler wrote:
On 11/19/2010 3:36 AM, Christopher Schmidt wrote:
We got an issue in Spirit. I am responsible for that. See these posts
http://article.gmane.org/gmane.comp.parsers.spirit.devel/3874 http://article.gmane.org/gmane.comp.parsers.spirit.devel/3875
for more information. There is completely new, partially broken code that does not interfere with existing code. The fix is trivial and definitely does not worse things at all as the existing code is just plain wrong. It can't get worse than that.
Oh, it can get worse. :-) Honestly, I'm not of a mind to hold up the release for this. No existing code will be broken by this, is that correct? If only new functionality is broken, then folks can wait for a working version.
I feel the same way.
Yeah, just code that uses a new fusion feature (adapted 'abstract data types') will be affected.
Is there any chance to get the patch in 1.45 - or at least a note in the docs of Spirit linking to a trac ticket with the patch?
That depends on whether Beman has rolled the release already and whether you have a doc patch ready to go.
If Beman has rolled the release.. AN option would be to put something on the web site notes (and release posts).
As the release is finally on its way I do not want to interrupt the process. I created a track ticket and attached the patch to it. https://svn.boost.org/trac/boost/ticket/4871 Version is set to Boost 1.46.0, Milestone is set to Boost 1.47.0. The compile errors are pretty much straightforward and I guess spirit users will search the trac tickets first. I am sorry for the inconveniences. Best regards, Christopher