Howdy fellow boosters, Several years ago I started using array_traits. I gathered from some later discussion that this library was never meant to be part of boost. However, I really like the library and find it more useful than the array<> implementation. Point in fact, array_traits and array<> overlap but probably weren't meant to solve the same problems [1]. Is array_traits around any more? I seem to recall something more general purpose. Maybe container_traits? Is this still being actively worked on? I am planning on (finally) upgrading our use of boost to a more recent version. I'm trying to work out what to do about our use of array_traits. Maybe I'll just keep using it. ...Duane [1] The primary difference between array_traits and array<> is the "construction" of the array. array_traits in fact has no construction. It can work with any arbitrary defined C-array of objects. array<> on the other hand requires construction. For my use,the major advantage that array_traits has over array<> is that I can refer to any ordinary C- array; in particular arrays that may not be under my control. Where as array<> requires that I change the type of the object.
"Duane Murphy"
Howdy fellow boosters, Several years ago I started using array_traits. I gathered from some later discussion that this library was never meant to be part of boost. However, I really like the library and find it more useful than the array<> implementation. Point in fact, array_traits and array<> overlap but probably weren't meant to solve the same problems [1].
Is array_traits around any more? I seem to recall something more general purpose. Maybe container_traits?
Thorsten Ottosen's Collection Traits library is the successor to array_traits. It was recently approved for inclusion in Boost and has been renamed Boost.Range. There was a note several days ago on the developers list that Boost.Range would be included in the next release but only 'unofficially', with no link to it on the libraries page. A version of the library is in the current CVS. See docs at http://cvs.sourceforge.net/viewcvs.py/boost/boost/libs/range/doc/. Jonathan
"Jonathan Turkanis"
"Duane Murphy"
wrote in message news:20040718042011.21634@linux.murphyslogic.com... Howdy fellow boosters, Several years ago I started using array_traits. I gathered from some later discussion that this library was never meant to be part of boost. However, I really like the library and find it more useful than the array<> implementation. Point in fact, array_traits and array<> overlap but probably weren't meant to solve the same problems [1].
Is array_traits around any more? I seem to recall something more general purpose. Maybe container_traits?
Thorsten Ottosen's Collection Traits library is the successor to array_traits. It was recently approved for inclusion in Boost and has been renamed Boost.Range.
There was a note several days ago on the developers list that Boost.Range would be included in the next release but only 'unofficially', with no link to it on the libraries page.
A version of the library is in the current CVS. See docs at http://cvs.sourceforge.net/viewcvs.py/boost/boost/libs/range/doc/.
Which of those .htm[l] files is up-to-date? -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
"David Abrahams"
"Jonathan Turkanis"
writes:
A version of the library is in the current CVS. See docs at http://cvs.sourceforge.net/viewcvs.py/boost/boost/libs/range/doc/.
Which of those .htm[l] files is up-to-date?
I'm not sure how up-to-date they are, but they were added within the last three weeks. Judging just by the title 'Collection Traits', they abviously don't incorporate all the changes agreed during the review. I posted the link as the most recent version I know of. Jonathan
participants (3)
-
David Abrahams
-
Duane Murphy
-
Jonathan Turkanis