- Boost - lists.boost.org

Re: [boost] Fwd: Summer of Code Update
by Gail Banaszkiewicz 21 Mar '07

21 Mar '07

[This was the text that was supposed to be in the email. I know Herve got it because he already replied. Sorry it came through blank.] Hervé, let's be sure to keep in touch! Perhaps we can work together for the next Summer of Code or even before then. I could still put in an application to Boost for some geometry stuff if you think it's worthwhile; I just figured that given the competitive nature of the past proposals, I wouldn't have enough time to put together a proposal that would stand out (particularly because I haven't used Boost all that much yet). Gail me22 wrote: > Your message came through blank. > > On 3/20/07, Gail Banaszkiewicz <gbanaszk(a)connect.carleton.ca> wrote: >> >> _______________________________________________ >> Unsubscribe & other changes: >> http://lists.boost.org/mailman/listinfo.cgi/boost >>

2 1

Google Summer of Code SVG Project [Boost]
by alex prince 21 Mar '07

21 Mar '07

2 1

[sorting] Assembly language radix sort uploaded with proper c++ header file and asm file
by Sam Schetterer 21 Mar '07

21 Mar '07

I have uploaded the assembly language version of radix sort to vault, along with the appropriate header file. However, please re-write the header file as needed for proper linkage.

1 0

[sorting] Multikey quicksort terminating object
by Sam Schetterer 20 Mar '07

20 Mar '07

Hi. I am writing multikey quicksort, which is like radix quicksort except for arrays of any type. However, multikey quicksort need a terminatiing object. I am not sure whether to have users pass the terminating value and trust that it will compare low against everything else, or whether I should have users create a class that is convertible to the object type being sorted, but will always compare low no matter what. Then, users will append either the terminating value or the special object to the end of each array and sort the arrays. I would like your input so that I can get started on the documentation for multikey quicksort. Also, I have posted an example version on vault in multikey quicksort.cpp. I know that the abilities offered by multikey quicksort aren't offered by std::sort.

1 0

typo in wave/util/flex_string.hpp
by Neal Becker 20 Mar '07

20 Mar '07

Surely this is a typo: ./boost/wave/util/flex_string.hpp:1644: warning: statement has no effect flex_string& append(const value_type* s, const size_type n) { Invariant checker(*this); checker;

2 1

Review of Intrusive library begins today March 12
by Joaquín Mª López Muñoz 20 Mar '07

20 Mar '07

The review of Ion Gaztañagas's Intrusive library begins today, March 12, and extends up to March 21. * Download: Boost vault: http://boost-consulting.com/vault/ Folder: Containers File: intrusive.2007-03-04.zip * Online docs: http://ice.prohosting.com/newfunk/boost/libs/intrusive * Description: Intrusive is a library presenting some intrusive containers to the world of C++. While intrusive containers were and are widely used in C, they became more and more forgotten in C++ due to the presence of the standard containers, which don't support intrusive techniques. Intrusive not only reintroduces this technique to C++, but also encapsulates the implementation in STL-like interfaces. Hence anyone familiar with standard containers can easily use Intrusive. Like their STL-counterparts, intrusive containers use template parameters to control the stored data types and some special aspects of intrusive containers. * Compilers tested (so far): Visual 7.1/WinXP Visual 8.0/WinXP GCC 4.1.1/MinGW Intel 9.1/WinXP GCC 4.1.2/Linux * Review questions: Here are some questions you might want to answer in your review: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? And finally, every review should answer this question: - Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. I invite you to submit your review, either publicly to the developers or the users lists, or else, if for whatever reason you don't want to publicize it, directly to me. Thank you for investing some of your time on reviewing Ion Gaztañaga's Intrusive library. The Review Manager, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

5 8

Re: [boost] Fwd: Summer of Code Update
by Gail Banaszkiewicz 20 Mar '07

20 Mar '07

1 0

[Boost-bugs] [ boost-Patches-1684708 ] add shared_ptr< const T> support
by SourceForge.net 20 Mar '07

20 Mar '07

Patches item #1684708, was opened at 2007-03-20 22:27 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=307586&aid=1684708&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Python Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Roman (roman_yakovenko) Assigned to: David Abrahams (david_abrahams) Summary: add shared_ptr< const T> support Initial Comment: This patch adds support to Boost.Python library to handle boost::shared_ptr< const T> class. The problem and solution were discussed in this thread: http://mail.python.org/pipermail/c++-sig/2006-November/011626.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=307586&aid=1684708&group_… ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[libpoet] active objects library release
by Frank Mori Hess 20 Mar '07

20 Mar '07

The interface of libpoet (an active object library) has started to settle down, so I've put a tarball in the boost vault to encourage people to try it out. Download: http://www.boost-consulting.com/vault/index.php?direction=0&order=&director… Online documentation: http://www.comedi.org/projects/libpoet/index.html -- Frank

1 0

Re: [boost] [Boost-announce] Review of Intrusive library begins today
by brangdon＠cix.compulink.co.uk 20 Mar '07

20 Mar '07

In-Reply-To: <45F5011E.8484B515(a)tid.es> joaquin(a)tid.es wrote (abridged): > The review of Ion Gaztañagas's Intrusive library begins today I have spent half an hour reading the documentation. Overall I like it. I have some questions and comments. Is there any reason why Destroyers must destroy? It seems to me you could have a Destroyer which pushed the value onto another list. Is that right? If so, is it a reasonable thing to do? If so, perhaps "Destroyer" is not the best name. I'd suggest "Sink" instead. Could remove_and_destroy take a default Destroyer argument that deleted the value? I hate the name "current" for the function that turns a value into an iterator. I'd prefer "to_iterator" or "as_iterator" or similar. "Current" just doesn't seem relevant to what it does, and the core thing it does is not indicated by that name. Did you consider having pop_back() return a reference to the value popped? As I understand it, the usual reasons why this a bad thing don't apply here; returning a reference cannot throw, and the value referred to isn't deleted. Did you consider making it easier to use as a replacement for list<value*> ? The semantics are already close, but the intrusive lists use references where the non-intrusive ones use pointers. I can see me having to edit out a lot of asterixes in my existing code. I was going to ask whether it would have been a good idea to allow a value type to be in several lists of the same type, but the more I think about it the more I agree that requiring the lists to be different types is best. I agree with Tom Brinkman that the introduction page of the documentation could do more to motivate the library. The core idea of using memory in the value type to store container-specific data, which is what makes the container "intrusive", needs to be mentioned earlier. I was pleased to see you mention the typical size overheads for values and containers. It seemed to me that the overhead for containers was a bit buried. I'd recommend you draw up a little comparison table which listed typical overheads for each type of container - hopefully including a good implementation of std containers if that's not too controversial. I would also like to see some speed measurements comparing std with intrusive lists and vectors. Obviously user's milage will vary, but given that performance is a major motivation for using this library I'd like to see at least some empirical indication that it can be faster. Regardless of the above I vote that Intrusive be accepted as a boost library. I am fairly knowledgable of the domain, having spent a lot of time using intrusive lists in C 20 years ago. My current app has some rigid data-structures currently based on std::list which could probably benefit from intrusive lists, but I'm not currently in a position to try this so the above is based only on reading the online documentation. > To: boost(a)lists.boost.org, boost-users(a)lists.boost.org, > boost-announce(a)lists.boost.org > Reply-To: boost-announce(a)lists.boost.org Incidently, I tried to send this message by replying, and my mail software used the Reply-To: field and sent it to boost-announce, where it was (unsurprisingly) rejected. Maybe Reply-To: could be set to boost(a)lists.boost.org instead? -- Dave Harris, Nottingham, UK.

2 1