March 2006 - Boost-users - lists.preview.boost.org

Newbie: Boost for Windows
by John Read 23 Mar '06

23 Mar '06

I have to work on Windows, but I don't have any idea about compilers and environments on this platform. My preference would be to use a CygWin environment with MinGW's gcc compiler to facilitate setting up a scripted nightly build incorporating Boost and my own code. Some others might want to use native Microsoft compilers and tools though. Steps so far: 1) Got/installed MinGW: MinGW-5.0.0.exe 2) Got/installed Boost: boost_1_33_1.exe 3) Opened Cygwin terminal and added MinGW/bin to path 4) cd-ed to boost_1_33_1/tools/build/jam_scr 5) . build.sh > result.txt Got these errors in results.txt: ### ### Using 'gcc' toolset. ### rm -rf bootstrap mkdir bootstrap gcc -o bootstrap/jam0 command.c compile.c execnt.c execunix.c execvms.c expand.c filent.c fileos2.c fileunix.c filevms.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execunix.c:19:24: sys/times.h: No such file or directory execunix.c: In function `execwait': execunix.c:187: error: storage size of 'old_time' isn't known execunix.c:187: error: storage size of 'new_time' isn't known fileunix.c:95:17: ar.h: No such file or directory fileunix.c: In function `file_archscan': fileunix.c:232: error: storage size of 'ar_hdr' isn't known fileunix.c:241: error: `SARMAG' undeclared (first use in this function) fileunix.c:241: error: (Each undeclared identifier is reported only once fileunix.c:241: error: for each function it appears in.) fileunix.c:242: error: `ARMAG' undeclared (first use in this function) I suspect that there is more involved in getting a proper Windows development environment set up. Can anyone point me in the right direction? A simple list of steps would be great. If none exists, I will provide one to the group once I have this sorted out. Thanks, John __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Re: [Boost-users] portable uuid generator - seed
by Oliver.Kowalke＠infineon.com 23 Mar '06

23 Mar '06

Hi Andy, as you mentioned in t he source std::time(0) is not a good truly-random seed. Maybe you could use boost::posix_time::microsec_clock::universal_time().time_of_day().total_ nanoseconds() ? Regards, Oliver >hi andy, > >On Fri, 2006-03-03 at 14:26 +0000, Andy Tompkins wrote: >> I am currently working on a guid class. It is not quite done yet, but >> is quite >> functional. It does have a portable function to create guids. I have >> put it >> in the boost vault (guid.zip) in the hopes that it may one day be a >> boost >> library. > >well, the api looks really good (very similar to my libuuid wrapper) ... >but i'm a bit lost building it ... >i guess i have to run bjam, but how do i have to use it? up to now i was >just using emerging boost, but i have to experience in building it :-/ > >thanks ... tim > >-- >TimBlechmann(a)gmx.de ICQ: 96771783 >http://www.mokabar.tk > >Linux is like a wigwam: no windows, no gates, apache inside, stable.

3 2

Re: [Boost-users] asio review results - asio accepted
by RIVASSEAU Jean Noel 23 Mar '06

23 Mar '06

Thanks, actually I wrote the first message because I do not have access to the web right now, and would have liked a short explanation on the ML, but I should have explained that... I'll have a look at it this evening. Jean-Noël -----Message d'origine----- De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Markus Schöpflin Envoyé : jeudi 23 mars 2006 15:39 À : boost-users(a)lists.boost.org Objet : Re: [Boost-users] asio review results - asio accepted RIVASSEAU Jean Noel wrote: > Could you just explain very shortly what Asio is about ? See http://asio.sourceforge.net/ Markus _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 1

Re: [Boost-users] asio review results - asio accepted
by RIVASSEAU Jean Noel 23 Mar '06

23 Mar '06

Could you just explain very shortly what Asio is about ? Jean-Noël -----Message d'origine----- De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Jeff Garland Envoyé : jeudi 23 mars 2006 15:18 À : boost-users(a)lists.boost.org Objet : [Boost-users] asio review results - asio accepted Cross-post from development list ---- All - I'm pleased to announce that asio has been accepted into Boost. As usual with a Boost review, the asio review generated plenty of discussion, issues, and controversy. Comments ranged from high praise, including success stories of projects in production, to serious design concerns and issues. On balance, in my judgment, asio provides a generally solid library that is ready for inclusion into the Boost library -- providing key functionality in an area that developers have a strong need. Of course, like anything else, asio is not perfect -- a number of key issues were uncovered during the review. In terms of required changes I'm only going to cite a few: - Fixes to dynamic memory allocation issues - Interface changes to support ipv4 and ipv6 seamlessly at runtime - Improvements to support strongly typed socket interfaces Chris has communicated a couple possible solutions to the memory allocation issue and I'll ask that the interface and other changes for this issue continue to be discussed on the Boost list so consensus can be achieved on the best resolution. Other key improvements that should be explored as future enhancements include: - Possible removal of some of the c-style interfaces - Exploration of higher level iostream integrations - Performance improvements - Improved documentation (wouldn't be Boost w/o this one) Chris has a much longer list of changes garnered from the review and is well on his way to addressing many of them. Note that there were several threads and discussions about performance, which is particularly critical for the domain covered by asio. One of the performance issues is the dynamic memory allocation issue cited above. In general, the reviewers have extremely high expectations here. However, after reviewing the discussion and library it's my belief that many developers will find asio performance sufficient to build significant projects with only the memory allocation changes. I expect Chris will be able to address some of the other performance issues cited by reviewers in asio over time. Once again I'll apologize to the Boost community for the delay in the review results. The delay was entirely due to my own personal scheduling issues and should not reflect on asio in any way. Thanks again to all the reviewers for their effort and especially to Chris for his tremendous effort in bringing asio to Boost! Jeff _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 1

asio review results - asio accepted
by Jeff Garland 23 Mar '06

23 Mar '06

Cross-post from development list ---- All - I'm pleased to announce that asio has been accepted into Boost. As usual with a Boost review, the asio review generated plenty of discussion, issues, and controversy. Comments ranged from high praise, including success stories of projects in production, to serious design concerns and issues. On balance, in my judgment, asio provides a generally solid library that is ready for inclusion into the Boost library -- providing key functionality in an area that developers have a strong need. Of course, like anything else, asio is not perfect -- a number of key issues were uncovered during the review. In terms of required changes I'm only going to cite a few: - Fixes to dynamic memory allocation issues - Interface changes to support ipv4 and ipv6 seamlessly at runtime - Improvements to support strongly typed socket interfaces Chris has communicated a couple possible solutions to the memory allocation issue and I'll ask that the interface and other changes for this issue continue to be discussed on the Boost list so consensus can be achieved on the best resolution. Other key improvements that should be explored as future enhancements include: - Possible removal of some of the c-style interfaces - Exploration of higher level iostream integrations - Performance improvements - Improved documentation (wouldn't be Boost w/o this one) Chris has a much longer list of changes garnered from the review and is well on his way to addressing many of them. Note that there were several threads and discussions about performance, which is particularly critical for the domain covered by asio. One of the performance issues is the dynamic memory allocation issue cited above. In general, the reviewers have extremely high expectations here. However, after reviewing the discussion and library it's my belief that many developers will find asio performance sufficient to build significant projects with only the memory allocation changes. I expect Chris will be able to address some of the other performance issues cited by reviewers in asio over time. Once again I'll apologize to the Boost community for the delay in the review results. The delay was entirely due to my own personal scheduling issues and should not reflect on asio in any way. Thanks again to all the reviewers for their effort and especially to Chris for his tremendous effort in bringing asio to Boost! Jeff

1 0

SubjectObserver, boost::Signals and thread safety.
by James Hughes 23 Mar '06

23 Mar '06

I notice from the signals documentation that it is not yet thread safe - since I need a thread safe subjectobserver pattern, should I quickly knock one up (!) or is it likely that signals will be thread safe in the near future? James

1 0

[uBLAS + Serialization] Is This Safe?
by Wu Yinghui, Freddie 23 Mar '06

23 Mar '06

Hi all, I found that uBLAS doesn't have Serialization support built in. So in my code, I do the following: ===== snip ===== class A { typedef boost::numeric::ublas::c_vector<float, 3> container_t; public: // Other member functions... private: friend class boost::serialization::access; template <typename Archive> void serialize(Archive &ar, unsigned int version) { container_t::pointer data = data_.data(); container_t::value_type (*p)[3] = reinterpret_cast<container_t::value_type (*)[3]>(data); ar & boost::serialization::make_nvp("data", *p); } private: // The data field to be serialized container_t data_; }; ===== snip ===== While this code seems to be working on my machine, there is reinterpret_cast<> in place in order to grab the content of the vector, as you can see. So my question is: Is this way of performing serialization safe/ portable/ etc.? Any idea? Cheers, Freddie -- Wu Yinghui, Freddie Research & Development Software Engineer Volume Interactions Pte Ltd 1 Kim Seng Promenade, #12-01 Great World City East Tower Singapore 237994 Tel: +65 62226962 (Ext 216) Fax: +65 62226215 Email: yhwu(a)volumeinteractions.com URL: http://www.volumeinteractions.com Important: This message is intended for the recipient(s) addressed above. It contains privileged and confidential information. If you are not the intended recipient, please notify the sender immediately by replying to this message and then delete it from your system. You must not read, copy, use, or disseminate this communication in any form. Thank you.

1 0

Boost Integer Traits 64-bit Support
by Wu Yinghui, Freddie 23 Mar '06

23 Mar '06

Just a quick question, does Boost integer traits classes support 64-bit integral types? I didn't seem to be able to get the following code compile: #include <boost/integer.hpp> #include <boost/integer/integer_mask.hpp> typedef typename boost::int_t<64> int_type; typedef boost::high_bit_mask_t<63> high_bit_type; I know that I can use boost::int64_t, but the problem is that the "64" here is not fixed in my code. It is dependent on some other parameters, so it could be 32 too. Am I missing anything? Cheers, Freddie -- Wu Yinghui, Freddie Research & Development Software Engineer Volume Interactions Pte Ltd 1 Kim Seng Promenade, #12-01 Great World City East Tower Singapore 237994 Tel: +65 62226962 (Ext 216) Fax: +65 62226215 Email: yhwu(a)volumeinteractions.com URL: http://www.volumeinteractions.com Important: This message is intended for the recipient(s) addressed above. It contains privileged and confidential information. If you are not the intended recipient, please notify the sender immediately by replying to this message and then delete it from your system. You must not read, copy, use, or disseminate this communication in any form. Thank you.

4 4

Re: [Boost-users] [Unit-Test] How to test private functions
by Shugar, Ben USC-RR 22 Mar '06

22 Mar '06

Try calling it inside a constructor or calling them from inside a public test method. Remember the publis test method is just for that purpose -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Leif Gruenwoldt Sent: Wednesday, March 22, 2006 11:55 AM To: boost-users(a)lists.boost.org Subject: [Boost-users] [Unit-Test] How to test private functions Is there a way to test the private functions of a class without moving them into public scope during test? What are some strategies for this? I was hoping to add "friend class boost::unit_test::test_suite;" to my class but that didn't work. -- Leif Gruenwoldt _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

[iostreams] inverse and "stateful" filters
by EMalenfant＠interstarinc.com 22 Mar '06

22 Mar '06

Hi, I wanted an InputFilter for removing comments from C++ source files. Since it seemed easier to write an OutputFilter, I decided to write that, and use iostreams::inverse to make an InputFilter out of it. However, it seems that inverse can't be used with "stateful" filters. Consider the following, using dictionary_output_filter from the tutorial: (http://www.boost.org/libs/iostreams/doc/index.html?path=2.2.6.3) namespace io = boost::iostreams; const std::string source("This foo will be bar"); io::example::dictionary dict; dict.add("foo", "bar"); io::filtering_istream in; in.push(io::invert(io::example::dictionary_output_filter(dict))); in.push(io::array_source(source.c_str(), source.length())); io::copy(in, std::cout); Output: This bar will be instead of the expected: This bar will be bar Is this a "known limitation"? Is there a workaround? Am I doing something silly? ----------------------------- Éric A conclusion is the place where you got tired of thinking

1 0