- Boost-users - lists.boost.org

[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

[iostreams] skip bug (repost)
by Phillip Seaver 01 Jun '07

01 Jun '07

I ran into a problem when using restrict on a file_source. The problem was that it decided that the stream wasn't seekable and called the version of skip that reads a character at a time until it gets to the requested offset, instead of just calling seek. The code was similar to this: namespace io = boost::iostreams; std::string filename; io::filtering_istream rstr(io::restrict(io::file_source(filename), 10, 100)); I've attached a patch that solved my problem. It was checking to see if the device was seekable (which means input_seekable and output_seekable), but since it was an input device, it was just input_seekable. Phillip Seaver --- skip.hpp.orig 2007-03-20 16:20:55.253000000 -0400 +++ skip.hpp 2007-03-20 16:11:51.096750000 -0400 @@ -67,7 +67,17 @@ void skip(Device& dev, stream_offset off) { typedef typename mode_of<Device>::type mode; - detail::skip(dev, off, is_convertible<mode, seekable>()); + typedef mpl::or_< + mpl::and_< + is_convertible<mode, input>, + is_convertible<mode, input_seekable> + >, + mpl::and_< + is_convertible<mode, output>, + is_convertible<mode, output_seekable> + > + > can_seek; + detail::skip(dev, off, can_seek()); } template<typename Filter, typename Device>

2 1

Problem with 1.34 Regex Package
by Jeffery Cavallaro 01 Jun '07

01 Jun '07

Hi, all! I am a bit of a newbie, so forgive if this has already been covered. The 1.34 regex package (or at least my build of it on FC6) appears to be broken. Please consider the following: #include <iostream> #include <iomanip> #include <boost/regex.hpp> int main(int argc, char *argv[]) { boost::regex rl("ab"); boost::regex ru("AB"); bool pass = regex_search("ab", rl); std::cout << std::boolalpha << pass << std::endl; pass = regex_search("AB", ru); std::cout << std::boolalpha << pass << std::endl; return EXIT_SUCCESS; } When built with 1.33 (as delivered with FC6), both tests return true. When built under 1.34 (downloaded and built), the uppercase test returns false. Yuck. Am I missing something? (probably...) -- Jeffery Cavallaro POSTINI Engineering Group 650-486-8342 ----------------------------------------------------------- This message may contain confidential and/or privileged information. This information is intended to be read only by the individual or entity to whom it is addressed. If you are not the intended recipient, you are on notice that any review, disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete or destroy any copy of this message.

1 1

newbie ordering question for boost::multi_index::ordered_non_unique
by Kevin McMahon 01 Jun '07

01 Jun '07

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. -kevin

1 0

[Boost.Test 1.34] Multiple instances of unit_test_log_t singleton
by Kolya 01 Jun '07

01 Jun '07

Hi, All! I am using Boost.Test library in my own application and I have included boost/test/unit_test.hpp in many my cpp-files. When I used boost version 1.33.1 all works fine. But in version 1.34 I have following compiler error: file1.obj : error LNK2005: "class unit_test_log_t::boost::unit_test_log_t & boost::unit_test::`anonymous namespace'::unit_test_log" (?unit_test_log@?A0xa35d3712@unit_test@boost@@3AAVunit_test_log_t@23@A) already defined in file2.obj After including boost/test/unit_test.hpp class unit_test_log has multiple instances. See boost/test/unit_test_log.hpp for details: BOOST_TEST_SINGLETON_INST( unit_test_log ) It means that following code will be included in many cpp-files! namespace { unit_test_log_t & inst = unit_test_log_t::instance(); } When I replace BOOST_TEST_SINGLETON_INST( unit_test_log ) in boost/test/unit_test_log.hpp with namespace {extern unit_test_log_t & unit_test_log;} and in one of my cpp-files add: namespace boost { namespace unit_test { BOOST_TEST_SINGLETON_INST( unit_test_log ) } } all works fine May be I do not understand something? Is there any legal workaround from this situation? I do not like touch boost core files by myself. Thank you! VC++ 7.1, boost 1.34, xp sp2.

4 6

Bind: more convenience operators?
by Arno Schoedl 01 Jun '07

01 Jun '07

Bind has operator! overloaded to allow convenient notting of bound functions. Is there a specific reason not to overload all other operators in a similar way, for example for defining an AND of two predicates f and g as boost::bind( f, _1 ) && boost::bind( g, _1 )? Arno

2 1