Legacy for compose?

Looking at the main index.html file in CVS, it looks like the old Compose library will be going away. However at least one book, _The C++ Standard Library: A Tutorial and Reference_ by Nicolai M. Josuttis in 1999, assumes that Compose will still be there (and improved over what's in the book). Shouldn't our library list page permanently keep a note over what happened to the Compose library (and what should replace it)? -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

Daryle Walker <darylew@hotmail.com> writes:
Looking at the main index.html file in CVS, it looks like the old Compose library will be going away. However at least one book, _The C++ Standard Library: A Tutorial and Reference_ by Nicolai M. Josuttis in 1999, assumes that Compose will still be there (and improved over what's in the book). Shouldn't our library list page permanently keep a note over what happened to the Compose library (and what should replace it)?
Good idea. Why not write one and check it in? -- Dave Abrahams Boost Consulting http://www.boost-consulting.com

On 9/1/04 4:26 AM, "David Abrahams" <dave@boost-consulting.com> wrote:
Daryle Walker <darylew@hotmail.com> writes:
Looking at the main index.html file in CVS, it looks like the old Compose library will be going away. However at least one book, _The C++ Standard Library: A Tutorial and Reference_ by Nicolai M. Josuttis in 1999, assumes that Compose will still be there (and improved over what's in the book). Shouldn't our library list page permanently keep a note over what happened to the Compose library (and what should replace it)?
Good idea. Why not write one and check it in?
Done. -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

On Tue, Aug 31, 2004 at 11:30:40PM -0400, Daryle Walker wrote:
Looking at the main index.html file in CVS, it looks like the old Compose library will be going away. However at least one book, _The C++ Standard Library: A Tutorial and Reference_ by Nicolai M. Josuttis in 1999, assumes that Compose will still be there (and improved over what's in the book). Shouldn't our library list page permanently keep a note over what happened to the Compose library (and what should replace it)?
That sounds very sensible to me. At the least the pages for the lib should be there as they might be cited in several books and articles. libs/compose.html could still redirect to libs/compose/index.html, which could just say: This library was deprecated in favor of the Bind or Lambda libraries and has been removed from Boost. (as attached file does) jon -- "It is seldom that liberty of any kind is lost all at once." - David Hume

On Wed, Sep 01, 2004 at 09:56:46AM +0100, Jonathan Wakely wrote:
On Tue, Aug 31, 2004 at 11:30:40PM -0400, Daryle Walker wrote:
Looking at the main index.html file in CVS, it looks like the old Compose library will be going away. However at least one book, _The C++ Standard Library: A Tutorial and Reference_ by Nicolai M. Josuttis in 1999, assumes that Compose will still be there (and improved over what's in the book). Shouldn't our library list page permanently keep a note over what happened to the Compose library (and what should replace it)?
That sounds very sensible to me.
At the least the pages for the lib should be there as they might be cited in several books and articles.
libs/compose.html could still redirect to libs/compose/index.html, which could just say:
This library was deprecated in favor of the Bind or Lambda libraries and has been removed from Boost.
(as attached file does)
jon
-- "It is seldom that liberty of any kind is lost all at once." - David Hume
/It2gYh: Permission denied
hmm ... dunno what happened there ... HTML attachment stripped? take two, index.htm renamed to index.txt jon -- "Consistency is the last refuge of the unimaginative." - Oscar Wilde

On 9/1/04 6:10 AM, "Jonathan Wakely" <cow@compsoc.man.ac.uk> wrote:
On Wed, Sep 01, 2004 at 09:56:46AM +0100, Jonathan Wakely wrote:
On Tue, Aug 31, 2004 at 11:30:40PM -0400, Daryle Walker wrote:
Looking at the main index.html file in CVS, it looks like the old Compose library will be going away. However at least one book, _The C++ Standard Library: A Tutorial and Reference_ by Nicolai M. Josuttis in 1999, assumes that Compose will still be there (and improved over what's in the book). Shouldn't our library list page permanently keep a note over what happened to the Compose library (and what should replace it)?
That sounds very sensible to me.
At the least the pages for the lib should be there as they might be cited in several books and articles.
libs/compose.html could still redirect to libs/compose/index.html, which could just say:
This library was deprecated in favor of the Bind or Lambda libraries and has been removed from Boost.
(as attached file does)
hmm ... dunno what happened there ... HTML attachment stripped?
take two, index.htm renamed to index.txt
I've added a note to the master library list. I noticed that my CVS copy of Boost doesn't have any Boost.Compose stuff in it. I have my settings to create or destroy directories as needed. That means that all the files for Boost.Compose have been deleted. We would have to resurrect the BOOST_ROOT/libs/compose/index.htm file (and its parent directory) before editing it. I'm not that good with CVS yet. Could someone who is good with CVS resurrect the file? (Or let me know how to do it myself.) And immediately replace it with Jon's text before committing? -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

Daryle Walker <darylew@hotmail.com> writes:
On 9/1/04 6:10 AM, "Jonathan Wakely" <cow@compsoc.man.ac.uk> wrote:
On Wed, Sep 01, 2004 at 09:56:46AM +0100, Jonathan Wakely wrote:
On Tue, Aug 31, 2004 at 11:30:40PM -0400, Daryle Walker wrote:
Looking at the main index.html file in CVS, it looks like the old Compose library will be going away. However at least one book, _The C++ Standard Library: A Tutorial and Reference_ by Nicolai M. Josuttis in 1999, assumes that Compose will still be there (and improved over what's in the book). Shouldn't our library list page permanently keep a note over what happened to the Compose library (and what should replace it)?
That sounds very sensible to me.
At the least the pages for the lib should be there as they might be cited in several books and articles.
libs/compose.html could still redirect to libs/compose/index.html, which could just say:
This library was deprecated in favor of the Bind or Lambda libraries and has been removed from Boost.
(as attached file does)
hmm ... dunno what happened there ... HTML attachment stripped?
take two, index.htm renamed to index.txt
I've added a note to the master library list. I noticed that my CVS copy of Boost doesn't have any Boost.Compose stuff in it. I have my settings to create or destroy directories as needed. That means that all the files for Boost.Compose have been deleted. We would have to resurrect the BOOST_ROOT/libs/compose/index.htm file (and its parent directory) before editing it. I'm not that good with CVS yet.
Could someone who is good with CVS resurrect the file? (Or let me know how to do it myself.)
Just cvs add the file and it will come back. HTH, -- Dave Abrahams Boost Consulting http://www.boost-consulting.com

On Tue, Sep 07, 2004 at 03:45:49PM -0400, Daryle Walker wrote:
I've added a note to the master library list. I noticed that my CVS copy of Boost doesn't have any Boost.Compose stuff in it. I have my settings to create or destroy directories as needed. That means that all the files for Boost.Compose have been deleted. We would have to resurrect the BOOST_ROOT/libs/compose/index.htm file (and its parent directory) before editing it. I'm not that good with CVS yet.
Could someone who is good with CVS resurrect the file? (Or let me know how to do it myself.) And immediately replace it with Jon's text before committing?
I don't have write access, but this is what you need to do: mkdir libs/compose cp new_version_of_index.htm libs/compose/index.htm cvs add libs/compose/index.htm cvs ci libs/compose/index.htm Where new_version_of_index.htm is the modified index.htm I sent, or something similar. The file revision numbering will continue from where it left off when the file was removed i.e. new version will be 1.6 jon
-- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- "You will find that the state is the kind of organization which, though it does big things badly, does small things badly too." - John Kenneth Galbraith

On Sep 14, 2004, at 6:38 AM, Jonathan Wakely wrote:
I don't have write access, but this is what you need to do:
mkdir libs/compose cp new_version_of_index.htm libs/compose/index.htm cvs add libs/compose/index.htm cvs ci libs/compose/index.htm
Where new_version_of_index.htm is the modified index.htm I sent, or something similar.
Done. My apologies for the delay. Doug
participants (4)
-
Daryle Walker
-
David Abrahams
-
Doug Gregor
-
Jonathan Wakely