[ceph.git] / ceph / src / boost / libs / spirit / classic / change_log.html

<html>
<head>
<title>Spirit Change Log</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="stylesheet" href="doc/theme/style.css" type="text/css">
</head>

<body>

<h2>Spirit Change Log</h2>
<h2>1.8.7</h2>
<ul>
  <li>Integrated the Spirit V1.8.x code base with Spirit V2. Spirit V1.8.x is
      now called 
    <strong>Spirit Classic.</strong> Even if the directory
      structure has changed (the 
    <strong>Spirit Classic</strong> 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.
    <br />
      The recommended way of using Spirit Classic is now to include header
      files from the directory '$BOOST_ROOT/boost/spirit/include'. All files of 
      <strong>Spirit Classic</strong>
      have now a 'classic_' prefixed to their name. For example the include
    <br/>
      <br><code>&nbsp;&nbsp;#include &lt;boost/spirit/core/core.hpp&gt;</code><br/> 
    <br/>
    now should be written as: 
    <br/>
       <br/><code>&nbsp;&nbsp;#include &lt;boost/spirit/include/classic_core.hpp&gt;</code><br/>
    <br/>      
    To avoid namespace conflicts with the new Spirit V2 library we moved <strong>Spirit
      Classic</strong> into the <tt>namespace boost::spirit::classic</tt>. This change will be automatically&nbsp;deactivated whenever the deprecated include files are
    being used. This ensures full backwards compatibility for existing applications.
    <br />
    For more details about this change please consult the documentation.</li>
</ul>
<h2>1.8.6</h2>
<ul>
Commit	Line	Data
7c673cae FG	1	<html>
	2	<head>
	3	<title>Spirit Change Log</title>
	4	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
	5	<link rel="stylesheet" href="doc/theme/style.css" type="text/css">
	6	</head>
	7
	8	<body>
	9
	10	<h2>Spirit Change Log</h2>
	11	<h2>1.8.7</h2>
	12	<ul>
	13	<li>Integrated the Spirit V1.8.x code base with Spirit V2. Spirit V1.8.x is
	14	now called
	15	<strong>Spirit Classic.</strong> Even if the directory
	16	structure has changed (the
	17	<strong>Spirit Classic</strong> headers are now moved to the
	18	'$BOOST_ROOT/boost/spirit/home/classic' directory), we created forwarding
	19	headers allowing to compile existing applications without any change.
	20	These forwarding headers are deprecated, though, which will result in
	21	corresponding warnings generated for each of the headers. The forwarding
	22	headers are expected to be removed in the future.
	23	<br />
	24	The recommended way of using Spirit Classic is now to include header
	25	files from the directory '$BOOST_ROOT/boost/spirit/include'. All files of
	26	<strong>Spirit Classic</strong>
	27	have now a 'classic_' prefixed to their name. For example the include
	28	<br/>
	29	<br><code>  #include <boost/spirit/core/core.hpp></code><br/>
	30	<br/>
	31	now should be written as:
	32	<br/>
	33	<br/><code>  #include <boost/spirit/include/classic_core.hpp></code><br/>
	34	<br/>
	35	To avoid namespace conflicts with the new Spirit V2 library we moved <strong>Spirit
	36	Classic</strong> into the <tt>namespace boost::spirit::classic</tt>. This change will be automatically deactivated whenever the deprecated include files are
	37	being used. This ensures full backwards compatibility for existing applications.
	38	<br />
	39	For more details about this change please consult the documentation.</li>
	40	</ul>
	41	<h2>1.8.6</h2>
	42	<ul>
	43