Hello,


I decided to post about mojo (Move of Joint Objects) II on this newsgroup
because the Standards committee will discuss the language change proposal
for move constructors submitted by David Abreahams, Peter Dimov, and Howard
Hinnant.

Mojo is a library- and convention-based approach to eliminating unnecessary
copying. The first version used some interesting tricks but crashed and
burned because the tricks prevented some common usage cases from
functioning.

Now the second version is available at http://moderncppdesign.com/mojo. From
a standardization viewpoint, I believe it serves as a good comparison
point - it illustrates how far a library-based solution can go. The
language-based solution should offer all the amenities of mojo (and more)
and none of the drawbacks.


Andrei

--
All new!  THE C++ Seminar: Oct. 28-30 in Vancouver, WA.
http://www.thecppseminar.com/



---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]