- Boost - lists.boost.org

in_place_factory0
by Vaclav Vesely 29 Mar '06

29 Mar '06

Hi, is there any reason for missing in_place_factory without arguments? I would like to write optional<my_class> mc(in_place()); I've wrote the code for this. But I can't modify the macro hell in "in_place_factory.hpp". Regards, Vaclav class in_place_factory0: public in_place_factory_base { public: in_place_factory0() {} template<class T> void apply(void* address) const { new(address) T(); } }; in_place_factory0 in_place() { return in_place_factory0(); }

2 2

[Boost-bugs] [ boost-Feature Requests-1460859 ] make timezone csv file C/C++ compatible
by SourceForge.net 29 Mar '06

29 Mar '06

Feature Requests item #1460859, was opened at 2006-03-29 10:27 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1460859&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: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: make timezone csv file C/C++ compatible Initial Comment: The timezone database file "date_time_zonespec.csv" is used for the boost date/time library, and is nominally intended to be read as a data file, by boost code, and possibly also by Excel or similar software. Because the file consists of quoted Ansi character strings, it could also be treated like an initialization value for a char *str[] string array, and used via an #include. However, since the data lines do not end with a comma, the last field of each line will get compile-time concatenated with the first field of the next line, thus thwarting this usage. I propose that either (1) the file be changed to add a comma at the end of each line, or (2) the file be changed to add an empty "" string as an extra (dummy) field at the end of each line. Method (2) has the advantage of remaining CSV file compatible, while still being a valid list of quoted strings for char *str[] string array. The dummy zero-length string at the end of each line would be compile-time concatenated with the first field of the next line, effectively eliminating it. Method (1) has the advantage of not adding an extra dummy field. As used by the boost code, the CSV parser would have to be modified to simply ignore the last (dummy) field or the trailing comma, whichever was implemented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1460859&group_… ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[asio] STLPort and std::vector<const Pod_Type>
by Felipe Magno de Almeida 29 Mar '06

29 Mar '06

Hi, STLPort doesnt seem to allow const-types as parameters to std::vector. It chokes in the std::allocator which define const_reference as const reference, making the two the same type. This creates multiple declarations for function-members: pointer address(reference __x) const { return &__x; } const_pointer address(const_reference __x) const { return &__x; } Is the STLPort right in this context or should something be done? This is making this code fails: std::vector<char> v(128); boost::asio::buffer(v); The problem is that even with non-const pod type boost::asio::buffer is instatiating std::vector<const char>. Thanks, -- Felipe Magno de Almeida

4 4

Re: [boost] asio review results -- asio accepted
by Bulygin, Sergey 29 Mar '06

29 Mar '06

"Christopher Kohlhoff" <chris(a)kohlhoff.com> wrote: > The current plan is for the next version to include breaking > interface changes arising from the review, plus some features on > which I would like to get more feedback (such as custom memory > allocation and dual IPv4/6 support). At that time, in addition > to the changelog, I will publish a list of review changes that > are yet to be made. Congrats, Chris and all relevant community! Is the Asio task list available somewhere to see what is likely to be changed, compared to the current 0.3.6 version? What is the suggested roadmap for those, who wish to adopt Asio right now? Should we use 0.3.6 as is, or should we consider those "breaking interface changes" since they are going to change conceptual library design? Best Regards, Sergey Bulygin PS Just as a minor hint for review wizard: it's time to change Asio status in formal_review_schedule.html from "Result Pending" to "Accepted".

2 1

problem when using boost::noncopyable_::noncopyable
by bwlee 29 Mar '06

29 Mar '06

I defined a class inherited from noncoyable and singleton, but when compiled by vc8.0(VC++ express 2005), it report a error like this: template<typename T> class thread_pool : boost::noncopyable, public boost::singleton { //... }; center\code\project.net\include\thread_pool.hpp(227) : error C2248: 'boost::noncopyable_::noncopyable::operator =' : cannot access private member declared in class 'boost::noncopyable_::noncopyable' c:\boost\include\boost-1_33_1\boost\noncopyable.hpp(28) : see declaration of 'boost::noncopyable_::noncopyable::operator =' c:\boost\include\boost-1_33_1\boost\noncopyable.hpp(22) : see declaration of 'boost::noncopyable_::noncopyable' This diagnostic occurred in the compiler generated function 'core::thread_pool<worker> &core::thread_pool<worker>::operator =(robert::core::thread_pool<worker> &)' with [ worker=core::worker_thread ] I wonder why it need to generate function overriding operator '='. Is there any simple solution?

2 1

reference counted object?
by Neal Becker 29 Mar '06

29 Mar '06

I wonder if we boost has anything useful for implementing reference counting (or other gc) for objects? I know we have shared_ptr, but I was interested in objects rather than pointers.

4 3

[iostreams] status report (and apology)
by Jonathan Turkanis 29 Mar '06

29 Mar '06

Dear Boosters, Thomas Witt wrote me this morning to alert me of some iostreams issues which need to be resolved for 1.34. While I knew that I had been neglecting my boost duties recently, I'm embarrassed to see how long it's been since I responded to post on this list. I'm going to try to resolve all the outstanding iostreams issues this week. I'll read through all the old post on this list and respond to them; if I miss some, please let me know. I hope to see some of you next week in Berlin! Best Regards, -- Jonathan Turkanis www.kangaroologic.com

1 0

[lambda] documentation error
by Edward Diener 29 Mar '06

29 Mar '06

In the lambda documentation, at the end of the "Construction and destruction" section, the wrapped expression for "delete_array()(p)" is given as "delete p[]". It should be "delete[] p".

1 0

[lambda] documentation spelling error
by Edward Diener 29 Mar '06

29 Mar '06

In the lambda documentation, the last line of the section "Lambda expressions for control structures" reads: "As more experience is gained, we may end up deprecating one or the other of these syntaces." The last word should be spelled "syntaxes" according to my dictionary.

1 0

Responsibility for orphaned libraries
by Keith MacDonald 28 Mar '06

28 Mar '06

The mysterious disappearance of Jonathan Turkanis (not heard from here since last October; home page says he's at UCB, but a directory search at UCB does not find him) set me wondering about the risk of using Boost libraries. Like iostreams, they are generally one-man works, which may be beyond an end user's ability or remit to maintain. Even if the author does not disappear, he may eventually lose interest or simply be too busy to maintain it forever, so do Boost have any procedures in place for such eventualities?

7 8