{"id":35,"date":"2009-10-31T09:23:48","date_gmt":"2009-10-31T16:23:48","guid":{"rendered":"http:\/\/boost-spirit.com\/home\/?page_id=35"},"modified":"2009-11-19T00:00:10","modified_gmt":"2009-11-19T08:00:10","slug":"news-archive","status":"publish","type":"page","link":"http:\/\/boost-spirit.com\/home\/info\/news-archive\/","title":{"rendered":"News Archive"},"content":{"rendered":"

October 20, 2008.<\/span><\/p>\n

IMPORTANT!!!<\/strong> PLEASE READ!!!<\/strong><\/span><\/p>\n

Regarding the evil post-skip (see news Post-skips (Important for Boost 1.34 and above users<\/em>)<\/span> <\/strong> below), here’s an ***IMPORTANT UPDATE***<\/strong>: I just found out that g >> eps_p is wrong. eps_p does not do a pre-skip, so the code will do nothing. The correct code is:<\/p>\n

parse ( str , g >> !end_p , skipper );<\/p><\/blockquote>\n

October 19, 2008<\/span>.<\/p>\n

Phoenix<\/strong><\/p>\n

Phoenix has been accepted into Boost!!! There are 15 votes, 11 of which vote for acceptance and 4 vote for conditional acceptance.<\/p>\n

All reviewers stated that the outstanding quality of the library and its documentation fully merit immediate acceptance. There is no direct concern with regard to the library itself. Phoenix V2 is already in the Boost distribution as a Spirit sub-library and has matured for a long time, proving its stability and usability. On the other hand, Phoenix provides functionality already covered by Boost.Bind and Boost.Lambda. It is the general intention to use Phoenix as the development ground for a new unified Boost library in this area. The review discussions revealed quite some details and certain problems which have to be resolved for this merger to happen. Joel has a full list of these details and promised to address all of them before adding Phoenix to the Boost SVN.<\/cite><\/p>\n

–Hartmut Kaiser, Review Manager<\/p><\/blockquote>\n

August 17, 2008<\/span>.<\/p>\n

Spirit2 and Boost 1.36.0 <\/strong><\/p>\n

Boost 1.36.0<\/a> has been released. Along with it, comes Spirit 1.8.7, integrated with Spirit V2, “The New Generation”. Even if the directory structure has changed (the Spirit Classic headers are now moved to the ‘$BOOST_ROOT\/boost\/spirit\/home\/classic’ directory), we created forwarding headers allowing to compile existing applications without any change. These forwarding headers are deprecated, though, which will result in corresponding warnings generated for each of the headers. The forwarding headers are expected to be removed in the future. The recommended way of using Spirit Classic is now to include header files from the directory ‘$BOOST_ROOT\/boost\/spirit\/include’. All files of Spirit Classic have now a ‘classic_’ prefixed to their name. For example the include<\/p>\n

#include <boost\/spirit\/core\/core.hpp><\/p>\n

now should be written as:<\/p>\n

#include <boost\/spirit\/include\/classic_core.hpp><\/p>\n

To avoid namespace conflicts with the new Spirit V2 library we moved Spirit Classic into the namespace boost::spirit::classic . This change will be automatically\u00a0deactivated whenever the deprecated include files are being used. This ensures full backwards compatibility for existing applications. For more details about this change please consult the documentation.<\/p>\n

Spirit2 is in beta. <\/strong>For the adventurous only<\/em>. The interface is stable (and has been for almost 2 years now). The documentation is still sparse, but there are tons of examples in there. Also, don’t complain about compile times. We haven’t optimized on compile times yet. There’s lots of room for improvement in that area still.<\/p>\n

April 18, 2008<\/span>.<\/p>\n

Spirit2 development<\/strong><\/p>\n

FYI, Spirit2 development has been moved to Boost SVN trunk<\/a>. We successfully merged with Spirit 1.8.x which is called “classic” Spirit now. Users of “classic” Spirit should not have to do anything; it’s fully backward compatible. However, there are changes in the include structure to accommodate different versions under one spirit directory at the same time. While the old includes will still work, they are deprecated with a warning message:<\/p>\n

“This header is deprecated. Please use: xxx.hpp”<\/p><\/blockquote>\n

The new include scheme is easy to use. We have an “include” directory where we place all forwarding headers to the actual files. For classic spirit, the files are prepended with “classic_”. For example, what used to be:<\/p>\n

“boost\/spirit\/core\/parser.hpp”<\/p><\/blockquote>\n

is now:<\/p>\n

“boost\/spirit\/include\/classic_parser.hpp”<\/p><\/blockquote>\n

November 28, 2007<\/span>.<\/p>\n

Post-skips (Important for Boost 1.34 and above users) <\/strong><\/p>\n

IMPORTANT!!!<\/strong> PLEASE READ!!!<\/strong><\/p>\n

In boost 1.34, if there is a trailing white space characters in an input sequence, parse returns with info.full set to false, even though parsing was (essentially) full. The skip parser is ignored for the last sequence. In 1.33 parsing succeeds as expected.<\/p>\n

The change in behavior was intentional. It was made on the grounds of consistency (parsers shouldn’t consume any more output than what they have matched), as well as to avoid a hang when directly parsing stdin: namely, parse() would hang waiting for a non-whitespace character at the end of a match.<\/p>\n

You may workaround this change by adding eps_p or end_p after your grammar, as in:<\/p>\n

my_grammar g ;
\nmy_skipper skipper ;
\nparse ( str , g >> eps_p , skipper ); \/\/ 1
\nparse ( str , g >> end_p , skipper ); \/\/ 2<\/p><\/blockquote>\n

The 2nd option requires a full match, while the first one gets you the previous behaviour without making a full match obligatory.<\/p>\n

Here’s where the change was first announced, for context:<\/p>\n

http:\/\/thread.gmane.org\/gmane.comp.parsers.spirit.general\/9839<\/a><\/p>\n

***IMPORTANT UPDATE***<\/strong>: I just found out that g >> eps_p is wrong. eps_p does not do a pre-skip, so the code will do nothing. The correct code is:<\/p>\n

parse ( str , g >> !end_p , skipper );<\/p><\/blockquote>\n

September 02, 2007<\/span>.<\/p>\n

Spirit 1.8.5 and 1.6.4 released<\/strong><\/p>\n

It is my pleasure to announce the release of Spirit 1.8.5 and 1.6.4 .<\/p>\n

Spirit 1.8.5 is a standalone variant of the version that is included in Boost 1.34.1; it doesn’t provide new features, but contains all the fixes that were applied since Spirit 1.8.4 . You can download Spirit 1.8.5 here<\/a>.<\/p>\n

Spirit 1.6.4 is the latest in a series of releases that are based on an earlier implementation that is friendlier towards older, less standard compliant compilers. This is a bug fix only release and is likely to be the final 1.6.x version. Spirit 1.6.4 is available here<\/a>.<\/p>\n

Both Spirit 1.8.5 and 1.6.4 are available in the following variants:<\/p>\n