- Boost-users - lists.boost.org

shared_ptr - no throw requirement
by Glen Knowles 18 Aug '03

18 Aug '03

What's the rational for the requirement that ~pointee() be no throw? Instead of nothrow could it have been specified that shared_ptr functions throw only if ~pointee() throws? This is also something that could go in the docs (assuming I didn't simply miss it). Thanks, Glen [Non-text portions of this message have been removed]

2 1

RE: [Boost-Users] RE: [date_time] library binaries for VC7.1? && Comm on lib placement
by Administrator 18 Aug '03

18 Aug '03

Dan, At least, so far, it only allows for debug/non-debug tagging. Right now, I'm starting to get involved over on the Boost.Build <http://groups.yahoo.com/group/jamboost/> mailing list. We'll see exactly how things pan out, although I doubt there will be any major changes for a little while. Dale > -----Original Message----- > From: Dan Muller [mailto:yg-boost-users@m.gmane.org] > Sent: Monday, August 18, 2003 6:00 AM > To: boost-users(a)yahoogroups.com > Subject: [Boost-Users] RE: [date_time] library binaries for VC7.1? && > Comm on lib placement > > > In article <41B553DE6D81D5119AD90050DA7ACF702E62E6@PDCSERVER>, > administrator(a)sbcltd.com says... > > Dan, > > > > The date_time.lib library is a static lib. The built > date_time.dll actually > > has no exports in it, so for VC purposes is useless. I > would say don't > > worry about it, and just use the static lib. > > Thanks, Dale, this is exactly what I needed to know. I was > starting to > worry that I didn't understand DUMPBIN's output, which would be > worrisome since I've been using it for years. :-) > > > On a side note, has anyone been working on placing built > items into a common > > directory, say <boost_top_dir>/lib? > > > > If not, I have a patch that should help alot. > > Sounds like an excellent idea. I'm assuming that on Windows, > the boost > build would then follow common conventions so that libraries > built with > different characteristics (debug vs. non-debug, multi- vs. single- > threaded, etc) had different names. (I haven't been following boost > build developments lately -- is this a topic of ongoing changes?) > > > > > > -----Original Message----- > > > From: Dan Muller [mailto:yg-boost-users@m.gmane.org] > [text elided] > > > > > > After building boost for VC7.1, I find a .lib file in > > > boost_1_30_0\libs\date_time\build\bin\libboost_date_time.lib\m > > > svc\debug > > > \runtime-link-dynamic and a .dll in > boost_1_30_0\libs\date_time\build > > > \bin\boost_date_time.dll\msvc\debug\runtime-link-dynamic. > > > > > > There are a couple of things that I don't understand about > > > these files. > > > > > > Is the .lib file supposed to be the import library for the > > > .dll? Linking > > > against the .lib file hasn't produced any import references in my > > > applications. Perhaps I'm just not hitting any out-of-line > > > functionality, but it sure seems like the .lib file is a > > > static library > > > rather than an import library. > > > > > > Also, running DUMPBIN /EXPORTS on the .dll file shows no exported > > > symbols related to date_time classes, as far as I can > see. It really > > > looks like it's exporting a bunch of stuff related to the > > > standard C++ > > > library, which makes no sense to me. > > > > > -- > Dan Muller > "So that's what an invisible barrier looks like!" (Time Bandits) > > > > ------------------------ Yahoo! Groups Sponsor > ---------------------~--> > Buy Ink Cartridges or Refill Kits for Your HP, Epson, Canon or Lexmark > Printer at Myinks.com. Free s/h on orders $50 or more to the > US & Canada. http://www.c1tracking.com/l.asp?cid=5511 > http://us.click.yahoo.com/l.m7sD/LIdGAA/qnsNAA/EbFolB/TM > -------------------------------------------------------------- > -------~-> > > Info: <http://www.boost.org> > Wiki: <http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl> > Unsubscribe: <mailto:boost-users-unsubscribe@yahoogroups.com> > > > Your use of Yahoo! Groups is subject to > http://docs.yahoo.com/info/terms/ > >

2 1

augmented_crc problem with gcc 3.1 and 3.2
by Raoul Gough 18 Aug '03

18 Aug '03

Hi, I've just noticed that my usage of boost::augmented_crc has stopped working since upgrading to gcc 3.x. The problem turns out to be with the workaround extra parameter BOOST_ACRC_DUMMY_PARM_TYPE*. The usage (in crc.hpp) looks like this: template < std::size_t Bits, BOOST_CRC_PARM_TYPE TruncPoly > typename uint_t<Bits>::fast augmented_crc( void const *buffer, std::size_t byte_count, typename uint_t<Bits>::fast initial_remainder BOOST_ACRC_DUMMY_PARM_TYPE ); Which doesn't supply a default value for the fourth parameter (i.e. it really requires all four parameters). Curiously, there is a BOOST_ACRC_DUMMY_INIT defined, which would supply a default value, but it is never used. Is this a bug in crc.hpp? *This happens for gcc 3.1 and 3.2 because config/compiler/gcc.hpp sets BOOST_NO_EXPLICIT_FUNCTION_TEMPLATE_ARGUMENTS to work around a known bug in those versions. -- Raoul Gough "Let there be one measure for wine throughout our kingdom, and one measure for ale, and one measure for corn" - Magna Carta

1 0

bgl compile problem with vc++ 7.1
by Stephan Höfer 18 Aug '03

18 Aug '03

Hello, I've checked out the newest version of boost from the cvs directory on boost-consulting.com. I've tried to recompile my bgl program to be able to use the latest changes of the bgl code. The compilation progress finished with the following error code: ..\..\..\boost\boost\graph\properties.hpp(169) : error C2248: 'boost::detail::subgraph_property_generator::bind_<SubGraph,Property,Tag>::type' : cannot access private typedef declared in class 'boost::detail::subgraph_property_generator::bind_<SubGraph,Property,Tag>' with [ SubGraph=boost::subgraph<boost::adjacency_list<boost::vecS,boost::vecS,boost::undirectedS,VertexProperty,EdgeProperty>>, Property=boost::detail::vertex_property_map<boost::subgraph<boost::adjacency_list<boost::vecS,boost::vecS,boost::undirectedS,VertexProperty,EdgeProperty>>,vertex_point_t>::Property, Tag=vertex_point_t ] and [ SubGraph=boost::subgraph<boost::adjacency_list<boost::vecS,boost::vecS,boost::undirectedS,VertexProperty,EdgeProperty>>, Property=boost::detail::vertex_property_map<boost::subgraph<boost::adjacency_list<boost::vecS,boost::vecS,boost::undirectedS,VertexProperty,EdgeProperty>>,vertex_point_t>::Property, Tag=vertex_point_t ] Cheers, Stephan [Non-text portions of this message have been removed]

2 1

[Q] Boost-Build V2
by Chris Drexler 18 Aug '03

18 Aug '03

Dear Listmembers, since a few weeks I'm using boost within a development system which should be changed towards operating system independence. As boost-buil V2 has a lot of nice features I wanted to base the build process on it. Unfortunatly it's very confusing to get all the information I need and sometimes it is not clear to which boost-build version (v1 or v2) some documentation belongs to. I hope this list is the right place to ask some questions about this. I'm going to describe the my current setup first (which is a little bit longish in order to cover all important points, hopefully) and afterwards I'll explain the problems. The scenario: We have some self-made class libraries which depend on downloaded packages (one is boost). So I thought of using the (usage-)dependency features of boost-build v2 for automatically using the right include paths and the according libraries. (I'm using milestone 6 of boost-build) root | + pkgs + boost_1_30_0 | | | + log4cpp_0.3.4b + include | + lib | + mylib + include | + src | + myapps + testapp + src The idea was to separate the information of which package versions to use and where libraries and include files reside. For this I put a Jamfile into 'pkgs' which consist of the following entries (OS independence not included right now) ------------------------------------------------------------------- project pkgs ; BOOST = boost_1_30_0 ; LOG4CPP = log4cpp-0.3.4b ; # system libraries lib winsock : : <name>Ws2_32.lib ; lib advapi : : <name>Advapi32.lib ; alias all : log4cpp boost ; alias boost : : <include>$(BOOST) ; lib log4cpp : : <file>$(LOG4CPP)/msvc6/log4cpp/Release/log4cpp.lib <variant>release : : <library>winsock <library>advapi ; lib log4cpp : : <file>$(LOG4CPP)/msvc6/log4cpp/Debug/log4cpp.lib <variant>debug : : <library>winsock <library>advapi ; ------------------------------------------------------------------- and the Jamfile in 'root' (where project-root.jam and boost-build.jam resides) contains ------------------------------------------------------------------- project MyProject : default-build debug <link>static ; use-project /pkgs : ./pkgs ; use-project /MyLib: ./mylib ; ------------------------------------------------------------------- The Jamfile in 'mylib' uses several of the libraries defined in 'pkgs' ------------------------------------------------------------------- project MyLib : usage-requirements <include>./include : requirements <include>./include : source-location ./src ; LIBSRC = [ .. whatever ..] ; lib MyLib : $(LIBSRC) : : : <library>/pkgs//log4cpp ; lib MyLib2 : $(LIBSRC) : : : <library>/pkgs//all ; ------------------------------------------------------------------- and the application 'testapp' depends on 'mylib' ------------------------------------------------------------------- project testapp : requirements <library>/MyLib//MyLib : source-location ./src ; exe test : testapp.cpp ; exe test2 : testapp.cpp : : <library>/MyLib//MyLib2 ; ------------------------------------------------------------------- Problems/Questions ================== - I had to put a (empty) 'project-root.jam' file into 'pkgs'. Otherwise I get the error message: error: default build can be specified only in first alternative main target is ../../../pkgs/log4cpp Any ideas why this happens? - the library dependcies for 'log4cpp' are correct and the appropriate library is linked BUT the include depencies are not used (neither for boost nor for log4cpp). I had to add the paths once more into the Jamfile in 'root' to make them available. After the changes the Jamfile looks like this ------------------------------------------------------------------- BOOST = pkgs/boost_1_30_0 ; LOG4CPP = pkgs/log4cpp-0.3.4b ; project MyProject : default-build debug <link>static : requirements <include>$(BOOST) <include>$(LOG4CPP)/include ; use-project /pkgs : ./pkgs ; use-project /MyLib: ./mylib ; ------------------------------------------------------------------- This is not what I wanted because now the paths to the package directies appear twice, once in root/Jamfile and once in root/pkgs/Jamfile. Thanks you very much ! Best Regards, Chris Drexler

2 3

RE: [Boost-Users] [date_time] library binaries for VC7.1? && Comm on lib placement
by Administrator 18 Aug '03

18 Aug '03

Dan, The date_time.lib library is a static lib. The built date_time.dll actually has no exports in it, so for VC purposes is useless. I would say don't worry about it, and just use the static lib. On a side note, has anyone been working on placing built items into a common directory, say <boost_top_dir>/lib? If not, I have a patch that should help alot. Dale > -----Original Message----- > From: Dan Muller [mailto:yg-boost-users@m.gmane.org] > Sent: Thursday, August 14, 2003 11:38 AM > To: boost-users(a)yahoogroups.com > Subject: [Boost-Users] [date_time] library binaries for VC7.1? > > > I've been using boost for a while, but now for the first time > I'm using > a component that isn't entirely header-based, namely > date_time in boost > 1.30.0. > > After building boost for VC7.1, I find a .lib file in > boost_1_30_0\libs\date_time\build\bin\libboost_date_time.lib\m > svc\debug > \runtime-link-dynamic and a .dll in boost_1_30_0\libs\date_time\build > \bin\boost_date_time.dll\msvc\debug\runtime-link-dynamic. > > There are a couple of things that I don't understand about > these files. > > Is the .lib file supposed to be the import library for the > .dll? Linking > against the .lib file hasn't produced any import references in my > applications. Perhaps I'm just not hitting any out-of-line > functionality, but it sure seems like the .lib file is a > static library > rather than an import library. > > Also, running DUMPBIN /EXPORTS on the .dll file shows no exported > symbols related to date_time classes, as far as I can see. It really > looks like it's exporting a bunch of stuff related to the > standard C++ > library, which makes no sense to me. > > Can anyone clear up my confusion? > > -- > Dan Muller > "So that's what an invisible barrier looks like!" (Time Bandits) > > > > ------------------------ Yahoo! Groups Sponsor > ---------------------~--> > Buy Ink Cartridges or Refill Kits for Your HP, Epson, Canon or Lexmark > Printer at Myinks.com. Free s/h on orders $50 or more to the > US & Canada. http://www.c1tracking.com/l.asp?cid=5511 > http://us.click.yahoo.com/l.m7sD/LIdGAA/qnsNAA/EbFolB/TM > -------------------------------------------------------------- > -------~-> > > Info: <http://www.boost.org> > Wiki: <http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl> > Unsubscribe: <mailto:boost-users-unsubscribe@yahoogroups.com> > > > Your use of Yahoo! Groups is subject to > http://docs.yahoo.com/info/terms/ > >

5 5

Type Traits
by Hossein Haeri 18 Aug '03

18 Aug '03

Hi friends, I'm looking for some stuff like the Loki::TypeTraits. I presume that there should be some similar ones in the boost repository. If I'm right, please tell me where they are. Thanks, --Hossein __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

4 5

uClibc and Boost
by codeazure 18 Aug '03

18 Aug '03

Has anyone had success using Boost with the uClibc libraries? In particular, have you got Boost.Python to work? I am using the getting_started1.cpp example provided with Boost. I am using Boost 1.30.0, uClibc 0.9.20 and Python 2.2.3. Note that uClibc does not currently support a dlopen() called library calling a dlopen(). I have found that as long as the library is loaded with Python, I can get it to work. I am currently using the SSL version of the socket module, which is using SSL libraries linked against Python. I have tried 2 techniques so far, but both result in core dumps. 1. Compile Python against uClibc and force linking with libboost_python.so 2. Compile Pyhton against uClibc only. Build Boost application by linking against libboost_python.a so no external library is needed. It may be that the 2 libraries are simply not compatible at this stage. Does anyone have any ideas? David Abrahams has suggested low level debugging to work out what is causing the core dump, but if the problem lies deep within uClibc, then I have a problem. Regards, Jeff Gray

2 1

Variant library or alternative suggestion
by vivek_arora 17 Aug '03

17 Aug '03

Whats is the status of the variant library which was supposed to have been approved for inclusion? I was unable to compile the code submitted for review. Are there any alternative ways/libraries for representing typesafe unions ? thanks -Vivek Arora

3 2

newbie metaprogramming question
by Istvan Buki 17 Aug '03

17 Aug '03

Hello Boost experts, I'm starting learning about template metaprogramming and I discovered that Boost provide several libraries in that area. I tried to see if those libraries could be used for a piece of code I have in my mind but I have a hard time figuring out how to start with it. I don't know if it is because I try to apply metaprogramming techniques in a use case where they doesn't fit or because of my lack of experience with these tools. I'm posting my use case here to get some help and advice about it. In a library I provide two classes: 1) An abstract base class (let's call it Base) from which user will derive their own classes. 2) A manager class responsible for manipulating instances of classes derived from Base. The user, in his application, create an an arbitrary number of classes derived from Base. Let's call them A, B and C for example. He create a typelist containing all those classes and passes it as a parameter to the manager class: typedef boost::mpl::list< A, B, C > my_types ; typedef Manager< my_types> my_manager ; When an instance of my_manager is created I would like to automatically create one instance of each type present in the typelist and these instances should be stored in a container where I could access them later. Something like the following: template < class Typelist > class Manager { public: Manager( void ) ; // ..... private: std::vector< Base * > container_ ; // .... } ; template < class Typelist > Manager< Typelist >::Manager( void ) { // This is not C++, it is pseudo-code that shows what I would // like to achieve. FOR EACH Typelist item i DO Base *b = new Typelist[i] container_.push_back( b ) ; END } So, at compile-time, some code should be generated to do what I wrote in pseudo-code in the constructor of Manager. Does this make any sense ? And if it is, could someone help me transform transform the pseudo-code in the constructor of manager to real code ? Thanks for any help you could provide, Istvan

1 0