June 2007 - Boost-users - lists.preview.boost.org

[multi_index] MSVS 2005 visualizers?
by Filip Konvička 04 Jun '07

04 Jun '07

Hi, I just wanted to know if anyone succeeded creating a visualizer for multi_index containers. I'd love to spend some time doing that for the good of the community (and my own, of course :-)), but I could not find any data members for exploration in the debugger's watch window. Any suggestions? See the following blog for more info: http://www.virtualdub.org/blog/pivot/entry.php?id=120 Some info can be found in the autoexp.dat file directly - there are pre-defined visualizers for eg. std::map (which works nice). Thanks, Filip

6 32

[date_time] UNICODE and wcout problems
by Filip Konvička 04 Jun '07

04 Jun '07

Hi, in MSVC 8.0 _UNICODE build, after I send a ptime to wcout, I can no longer print "international" characters. When I use a temporary wostringstream for printing the ptime, everything is OK. Minimal repro see below (the "2" at the end is never printed). With some characters like the "š" in the example, the output is totally cut off; with others, like "á", the codepage is changed, so the characters are displayed incorrectly. Any suggestions? Thanks, Filip // _UNICODE must be defined; the "2" is never printed. #include <string> #include <iostream> #include <sstream> #include <locale.h> #include <boost/date_time/posix_time/posix_time.hpp> using boost::posix_time::ptime; using boost::date_time::not_a_date_time; int main() { wstring intl=L"\x161"; wostringstream ss; ss << ptime(not_a_date_time); wcout << ss.str() << endl; wcout << intl << endl; wcout << L"1" << endl; wcout << ptime(not_a_date_time) << endl; wcout << intl << endl; wcout << L"2" << endl; }

4 10

[thread_safe_signals] won't compile on VC71
by David Matz 04 Jun '07

04 Jun '07

Hello, I'm very impressed from Mr. Hess' work on thread safe signals for the boost library. In my opinion it's a great step to provide thread safe signals in a common library like boost and I like to use it as replacement for third party libs. Unfortunately I going in trouble when using the latest version of this module (thread_safe_signals-2007-03-19.tgz which is the same as out of the cvs). I can't get it compile on Microsoft VS71. I tried with gcc and VS8 and it works but for the VS71 compiler which we are working it fails. As mentioned in the documentation I included the headers of thread_safe_signals before the normal boost headers which are in fact 1_33_1 (same results with 1_34_0). The I picked up a sample project signal_test.cpp from boost/test/ and start to compile it but it fails with the following compiler hints: Kompilieren... signal_test.cpp ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot0<R,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot1<R,T1,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot2<R,T1,T2,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot3<R,T1,T2,T3,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot4<R,T1,T2,T3,T4,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot5<R,T1,T2,T3,T4,T5,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot6<R,T1,T2,T3,T4,T5,T6,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot7<R,T1,T2,T3,T4,T5,T6,T7,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot8<R,T1,T2,T3,T4,T5,T6,T7,T8,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot9<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot10<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,SlotFunction>' The same error comes up with other example snippets like doc_view.cpp or something else. At this stage I can't understand what is going on. Any help is very welcome. -- David Matz ---------------------------- Software Developer Spatial View GmbH david.matz<at>spatialview.com registration court: Amtsgericht Dresden, HRB 21104 managing directors: Wolfgang Opel, Jens Wiegrebe

2 2

[interprocess]
by Aaron W. LaFramboise 03 Jun '07

03 Jun '07

I just got Boost.Interprocess working, and it's really an amazing library. Ion, it's obvious you've put a lot of time into this library, and the result is really nice. However, I've had these issues so far: (1) Is there a way to get a managed_shared_memory segment to tell me allocation statistics? What I'd like is something that can tell me. (a) Segment size (b) Allocated memory (c) Most importantly, free memory (2) It's been brought up before, but there seriously needs to be a way to grow managed shared memory segments. I understand that this is really tricky to implement, and probably just as tricky to use safely, but it's an important feature, in my opinion. I guess the main difficulties here are the potential change of base, and atomicity? (3) Regarding priv_open_or_create() in managed_open_or_create_impl.hpp, this implementation creates some small annoyances for me by throwing. I don't have any idea how to tell if POSIX O_CREAT actually created anything or not. However, I'm using Windows, and on Windows, you always can tell, as far as I know, both for file creation and named shared memory object creation. Would it be difficult to avoid throwing for the Windows case?

3 4

Re: [Boost-users] newbie ordering question forboost::multi_index::ordered_non_unique
by "JOAQUIN LOPEZ MU?Z" 02 Jun '07

02 Jun '07

Hello Kevin, ----- Mensaje original ----- De: Kevin McMahon <kevinmcm(a)alum.mit.edu> Fecha: Sábado, Junio 2, 2007 4:15 pm Asunto: [Boost-users] newbie ordering question forboost::multi_index::ordered_non_unique Para: boost-users(a)lists.boost.org > I'd like to pop items in my data set ordered by a key, but if the > key is identical then ordered in the order I inserted them. > Is there a good way to do that? I guess I could make a > composite key using an increasing id. Although it is not documented (and I think I should document it in light of LWG issue 233), non-hinted insertion always happens at the end of all previously stored elements with equivalent key. Is this what you want? Are you observing otherwise? Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

[date_time] nanosec resolution compile problem
by Christopher Lux 02 Jun '07

02 Jun '07

Hi, i am trying to use date_time with nanosec resolution for the fractional seconds part. So i define BOOST_DATE_TIME_POSIX_TIME_STD_CONFIG in my projects using date_time. Now i get the compiler warning below. I found out that the problem in the said function is that in boost/date_time/date_duration.hpp the struct duration_traits_adapted defines the int_type as long and not as int_64t. The warning is generated in the add_time_duration() funtion of the split_timedate_system class. So i imagine that this is a bigger issue, because if the durations get bigger than what a long can hold (what will happen fast with nanosec resolution) the problems will come. Can this be resolved with an small fix to the duration_traits_adapted struct or have there to be more fixes? Here the compiler warning (VS.net 2005 SP1) boost\boost/date_time/time_system_split.hpp(189) : warning C4244: 'initializing' : conversion from '__int64' to 'long', possible loss of data D:\_devel\schism_wc_x86\schism\projects\cmake\..\..\ext\inc\boost\boost/date_time/time_system_split.hpp(180) : while compiling class template member function 'boost::posix_time::simple_time_rep boost::date_time::split_timedate_system<config>::add_time_duration(const boost::posix_time::simple_time_rep &,boost::posix_time::time_duration)' with [ config=boost::posix_time::posix_time_system_config ] D:\_devel\schism_wc_x86\schism\projects\cmake\..\..\ext\inc\boost\boost/date_time/time.hpp(52) : see reference to class template instantiation 'boost::date_time::split_timedate_system<config>' being compiled with [ config=boost::posix_time::posix_time_system_config ] D:\_devel\schism_wc_x86\schism\projects\cmake\..\..\ext\inc\boost\boost/date_time/posix_time/ptime.hpp(32) : see reference to class template instantiation 'boost::date_time::base_time<T,time_system>' being compiled with [ T=boost::posix_time::ptime, time_system=boost::posix_time::posix_time_system ] -chris -- Christopher Lux | | Bauhaus University Weimar | Faculty of Media - Virtual Reality Systems Group

2 2

converting ptime to/from CLR (.NET) DateTime
by Jens Schluetter 02 Jun '07

02 Jun '07

Hi, I'm kinda stuck. I'm working on an inter op library to glue C++ code that uses ptime with C# code that uses (of course) the .NET DateTime format. Since the system needs the outmost performance I'm looking for a way to use binary conversion. Conversion from .NET to ptime is easy since there is a from_ftime<> conversion method, however the other direction is somewhat blocked since no ptime to FILE_TIME conversion exists. My current workaround is using ISO time strings but performance is somewhat dismal since there is a lot of string <> binary conversion. Does anyone know of a more straight forward (binary)way of converting? And just in case, using regular time_t as common denominator is not an option since at leas millisecond resolution is required. I'd be greatful for any recommendations/ideas. Cheers, Jens.

2 1

datetime istream and ostream operators don't match
by Lothar Werzinger 02 Jun '07

02 Jun '07

compile the attached cppunit test with -DHIDE_BOOST_DATETIME_BUGS=false to see where datetime ostream operator produces an output that the datetime istream operator can not digest. Lothar -- Lothar Werzinger Dipl.-Ing. Univ. framework & platform architect Tradescape Inc. 111 West St. John Street, Suite 200 San Jose, Ca 95113 email: lothar(a)tradescape.biz web: http://www.tradescape.biz

2 1

Requesting boost x64 getting started documentation
by Daniel Svensson 02 Jun '07

02 Jun '07

Would someone who know how to do it add information about how to build boost for x64 to the online "getting started" documentation. An example command line like "bjam address-model=64 install" would probably be sufficient. See the "Boost 1.34 and VC++ x64" thread; > > Cory Nelson wrote: >> >> This was pretty straightforward for 1.33, but 1.34 using BB2 seems to >> >> have changed things a bit. There doesn't seem to be any documentation >> >> on compiling 1.34 for x64 with VC++ - can anyone offer some insight? > > > > Yea, as with previous Boost.Build versions those options are not > > documented :-) Just add an "address-model=64" argument when building. > > > >

1 0

[BGL] boost::bind fails to compile when used with edge iterators in for_each
by Sashan Govender 01 Jun '07

01 Jun '07

Hi I'm trying to run a functor over edges from a graph using for_each however it fails when the iterators are edges. The same technique works for iterators to vertices. Here is the compiler error: g++ -o bind_edge_test bind_edge_test.cpp /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/bits/stl_algo.h: In function '_Function std::for_each(_InputIterator, _InputIterator, _Function) [with _InputIterator = boost::detail::undirected_edge_iter<std::_List_iterator<boost::list_edge<void*, boost::property<boost::edge_name_t, unsigned int, boost::no_property> > >, boost::detail::edge_desc_impl<boost::undirected_tag, void*>, int>, _Function = boost::_bi::bind_t<void, Op, boost::_bi::list2<boost::arg<1>, boost::_bi::value<int> > >]': bind_edge_test.cpp:79: instantiated from here /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/bits/stl_algo.h:159: error: no match for call to '(boost::_bi::bind_t<void, Op, boost::_bi::list2<boost::arg<1>, boost::_bi::value<int> > >) (boost::detail::edge_desc_impl<boost::undirected_tag, void*>)' I've attached the file. Thanks for the help. -- sashan http://sashang.orcon.net.nz/

3 3