|
Boost Users : |
Subject: [Boost-users] Intrusive list/ilist and rbtree marshalling support
From: Brian Wood (woodbrian77_at_[hidden])
Date: 2009-04-06 21:43:06
I'm happy to announce that version 1.8 of the C++ Middleware
This version adds support for the following:
* Exclusive marshalling support of boost::intrusive::list and
* Several new options on the user interface including:
+ An "Error Handling" option that indicates whether the code should
+ A "Code Structure" option that indicates whether the code should
+ A choice between unsigned short or unsigned int as the type for
* A mechanism to turn off automatic code generation for a type.
class bag
As the comment indicates, you will provide the implementation
Additionally, I would like to say that I find the Intrusive library to be
Brian Wood
"Then Samuel took a rock and set it up between Mizpah and Shen.
Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net
Writer is available on line --
http://webEbenezer.net/cgi-bin/samb.cgi
boost::intrusive::rbtree. Neither Boost Intrusive nor Boost
Serialization offer serialization support of the Intrusive
containers. Rather than having two types called 'list,' we
refer to boost::intrusive::list as an ilist. An example of this
support is here --
http://webEbenezer.net/rbtree_marshalling.html
be written using return codes or exceptions. The exception
support is new in this release. This option affects the signatures
of the generated marshalling functions.
be written in header-only format or separated interface and
implementation files. The separated interface and implementation
support is new in this release. This option also affects the
signatures of the generated marshalling functions.
constants written by the C++ Middleware Writer. Constants that
identify messages and user defined types are written by the
software. Previously the constants were always unsigned ints.
Adding a // comment within a class declaration with
"hand_written_marshalling_code" in the text of the comment will
disable default code generation for that type. For example,
{
// hand_written_marshalling_code
...
};
of the marshalling functions for this class. This option is
not available with /* */ comments.
sound and am using it internally in the C++ Middleware Writer. Thanks to
the authors: Olaf Krzikalla and Ion Gaztañaga.
Ebenezer Enterprises
www.webEbenezer.net <http://www.webebenezer.net/>
He named it Ebenezer [Rock of Help] and said, 'Until now the L-RD
has helped us.'"