- Boost - lists.boost.org

[steve@sumost.ca: [Boost-build] help with boost 1.35 variant specification]
by Steve M. Robbins 01 Apr '08

01 Apr '08

Anyone here know the answer? Thanks, -Steve ----- Forwarded message from "Steve M. Robbins" <steve(a)sumost.ca> ----- Date: Mon, 31 Mar 2008 15:07:49 -0500 From: "Steve M. Robbins" <steve(a)sumost.ca> To: boost-build(a)lists.boost.org Subject: [Boost-build] help with boost 1.35 variant specification Reply-To: "Boost.Build developer's and user's list" <boost-build(a)lists.boost.org> Hi, We have been building boost (up to 1.34.1) for Debian/linux using $(JAM) variant=release,debug threading=single,multi where $(JAM) is the path to bjam (built from the boost sources) together with the options -d2, --user-config and -sHAVE_ICU=1. The user config file contains: using gcc : 4.2 : g++-4.2 : <define>_REENTRANT ; using python : 2.4 : /usr ; using python : 2.5 : /usr ; This always resulted in four static libraries and four shared libraries for, say, the date-time library. With 1.35, however, I get the four shared libs but only one static lib: steve@riemann{boost_1_35_0}grep 'gcc.link.dll.*date' ../boost_1.35.0-1_i386.build gcc.link.dll bin.v2/libs/date_time/build/gcc-4.2/release/libboost_date_time-gcc42-1_35.so.1.35.0 gcc.link.dll bin.v2/libs/date_time/build/gcc-4.2/release/threading-multi/libboost_date_time-gcc42-mt-1_35.so.1.35.0 gcc.link.dll bin.v2/libs/date_time/build/gcc-4.2/debug/libboost_date_time-gcc42-d-1_35.so.1.35.0 gcc.link.dll bin.v2/libs/date_time/build/gcc-4.2/debug/threading-multi/libboost_date_time-gcc42-mt-d-1_35.so.1.35.0 steve@riemann{boost_1_35_0}grep 'gcc.archive.*date' ../boost_1.35.0-1_i386.build gcc.archive ../../../bin.v2/libs/date_time/build/gcc-4.2/release/link-static/threading-multi/libboost_date_time-gcc42-mt-1_35.a How do I get all 8 library builds back? I have read a couple of posts about --build-type=complete, so I tried adding that to $(JAM), but this gives a completely inpenetrable error: Skipping build of: ./headers <build>no in common properties Skipping build of: ./build_all <build>no in common properties Skipping build of: libs/regex/build/icucore <build>no in common properties Skipping build of: libs/regex/build/icuin <build>no in common properties Skipping build of: libs/regex/build/icudata <build>no in common properties /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/kernel/class.jam:93: in new *** argument error * rule object(searched-lib-target)(a)2059.__init__ ( name : project : shared ? : search * : action ) * called with: ( icudata icui18n icuuc : object(project-target)@212 : true : : object(null-action)@2058 : : : : ) * extra argument icui18n /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/tools/builtin.jam:349:see definition of rule '__init__' being called /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/tools/builtin.jam:592: in searched-lib-generator.run /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/tools/unix.jam:113: in object(unix-searched-lib-generator)(a)25.run /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/generators.jam:859: in try-one-generator-really /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/generators.jam:920: in try-one-generator /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/generators.jam:1131: in construct-really /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/generators.jam:1204: in generators.construct /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/tools/builtin.jam:496: in object(lib-generator)(a)5.run /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/generators.jam:859: in try-one-generator-really /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/generators.jam:920: in try-one-generator /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/generators.jam:1131: in construct-really /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/generators.jam:1204: in generators.construct /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/targets.jam:1368: in construct /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/targets.jam:1206: in object(typed-target)(a)224.generate /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/targets.jam:742: in generate-really /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/targets.jam:715: in object(main-target)(a)655.generate /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/targets.jam:254: in object(project-target)(a)212.generate /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/targets.jam:858: in targets.generate-from-reference /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/targets.jam:1129: in generate-dependencies /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/targets.jam:1179: in object(alias-target-class)(a)114.generate /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/targets.jam:742: in generate-really /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/targets.jam:715: in object(main-target)(a)376.generate /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build/targets.jam:254: in object(project-target)(a)70.generate /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/build-system.jam:658: in load /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/kernel/modules.jam:267: in import /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/tools/build/v2/kernel/bootstrap.jam:132: in boost-build /usr/local/src/Packages/boost/upstream/1.35/boost_1_35_0/boost-build.jam:11: in module scope make: *** [build-stamp] Error 1 What does this mean: did I invoke bjam incorrectly or is some jam file broken? Thanks, -Steve _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build ----- End forwarded message -----

1 0

[shifted_ptr] <T []> support, VC 8 certified, bug fix
by Phil Bouchard 01 Apr '08

01 Apr '08

Greetings: I got slowed down by a bug but fortunately I put my hands on it; - I fixed and updated the version in the Vault. - I have also made the headers compile fine under VC 8 but I haven't checked out the executable (missing objects). - I added safer support for array objects by limiting to access operator [] - I have replace "make_shifted_ptr" with "make_shifted_ptee" for efficiency reasons. It is possible to fall it back to its predecessor but requires some work, - I wanted to change the way sets are merge and did so. Todo: - Documentation. BTW I think Shifted Pointer got removed from the review schedule. I thought I didn't need documentation at that point but this is a short notice. Regards, -Phil

1 0

[gsoc 2008] JSON Archives for Boost.serialization
by Esteve Fernandez 01 Apr '08

01 Apr '08

Hi all, I'm new to this list but have been tracking Boost development for a long time. Never thought I could contribute something new to Boost, but after seeing this year's GSoC Boost proposal, I changed my mind and decided to take a deeper look at the JSON proposal. I've used the Boost.serialization library extensively and always end up needing something more portable than the binary archive and less heavyweight than the XML archive. Also, I spend a lot of time developing with Boost.Python and a format already supported by Python would be great, so seeing there was interest in a JSON archive was the perfect opportunity to join. Anyway, I've some points regarding this project before I apply, don't know if I should send them to Jeff (who suggested the idea) or to Robert (who implemented Boost.serialization). Instead of just bothering them, I'll bother all the subscribers to boost(a)lists.boost.org :-) - the JSON spec is quite simple, but given that it's a subset of YAML (actually Syck parses JSON as well), should it support it in the future as well? - what about Unicode? I know that Boost.Regex supports Unicode if compiled against ICU and the JSON spec states that everything must be in Unicode (correct me if I'm wrong) - TinyJSON and JSON.Spirit both use a MIT-like license (JSON.Spirit is licensed under CPOL). The Boost license is compatible with them but, could it pose a problem? There's JSONcpp [1] as well, which is public domain. - wading through the Boost mailing list archives, I found a message [2] by Daryle Walker in which he expressed interest in a JSON serializer some while ago (2005), but I think it wasn't discussed any further. Eric Newhuis wrote again about having a JSON archive just a few weeks ago [3] - which platforms must be supported? I can only provide support to GCC under Linux, but I guess it has to support MSVC and some other platforms. Will it have to be available for all the platforms supported by Boost at the end of the summer or is it more of a process? That is, given that one of the purposes of GSoC is to involve more people into free software/open source projects, whoever (I hope it's me :-)) implements the JSON serializer, will become its maintainer too and will take care of all the tasks related to accept patches, track bugs, add support for future/incomplete platforms, etc. - I thought of adding JSON support to Boost.Spirit as well. Currently it has support for printing ASTs in XML (see tree_to_xml). A JSON dumper would be quite useful for manipulating ASTs in a high level language, such as Python through Boost.Python Cheers. 1 - http://jsoncpp.sourceforge.net/ 2 - http://lists.boost.org/Archives/boost/2005/09/94438.php 3 - http://lists.boost.org/boost-users/2008/03/34336.php

5 6

[shifted_ptr] Now supports <void>, multithread roots & preprocessor code
by Phil Bouchard 01 Apr '08

01 Apr '08

Greetings: Ok, this a nice feature that just got added to the pointer. I just added support for "void" pointers and works perfectly. We can see the object being deleted correctly after the shifted_ptr<void> is destructed. Furthermore a very nice property shifted_ptr_base has is that it can be casted to a regular pointer and back again to a shifted_ptr_base and the pointee will still be correctly deallocated. I never saw any production code using perfect C++ coding and sometimes it happens we rely on "working undefined behaviors". Multithreaded support has been added but unfortunately I didn't see any function returning the current thread id. Was this disregarded? Finally I am using cleaner preprocessor coding for variadic function templates: http://www.boost-consulting.com/vault/index.php?action=downloadfile&filenam… Thanks, -Phil

3 8

Interest in static initialization library
by Sean Hunt 01 Apr '08

01 Apr '08

Hi Boosters! I was wondering if there is any interest for a static initialization library. The idea I currently have might look something like this: #include <iostream> #include <boost/init.hpp> using namespace boost; using namespace std; class myType { myType(int i) { cout<<"myType constructed with parameter "<<i<<endl; } }; void myFunc (int i) { cout<<"myFunc called with parameter "<<i<<endl; } extern init::variable<myType> myVar (42); init::function<void (), myVar> myInitFunc (myFunc, 35); init::variable<myType> myVar; int main () { init::init(); } The extern declaration of myVar simulates a global defined in a different translation unit - in this case, function is by the standard guaranteed to be initialized first, but if myVar is in a different TU, then the output is undefined. By passing myVar as a parameter to the function template, the library will ensure that the function is called after the variable (I was originally considering using a before<myVar> and after<myVar> syntax, but it would be too difficult to implement an algorithm that would be guaranteed to get the order right, whereas it's quite easy like this). The idea would be to allow an easy relationship for static initialization. I'm thinking that the variable class should act as a near-transparent wrapper by overloading all the operators. Since operator . is not overloadable, I would probably allow it to act through ->, unless the member is a pointer-like type (the exact definition of pointer-like could be controlled using template specializations). A member function would obviously be provided for accessing the object directly (such as to call a smart pointer's functions). Another idea is to have two separate classes (say, variable and wrapper), and only one has the wrapping behavior - the other has to have explicit access each time. The init function serves as the trigger for all the static initialization to occur (earlier actual initializations serve only to add the initializer to the queue) Functors would be provided to defer a function call (to get a constructor or function parameter) until the time that the initialization of the object takes place, rather than the initializer. If an exception is thrown, the initialization library will remember its state and then a subsequent call would take it off where it stopped. (adding new objects to the queue once initialization has begun would be allowable, allowing the initializer to be reused). Someone will no doubt at some point argue that I should wrap the functionality in a class to handle the initialization in order for different code to simultaneously take advantage of the facility, but I will dismiss that because it would fall prey to static initialization order and not work as intended. Perhaps later I will add a system that allows user code to store the current initialization list/state, but I don't think it would be worth the effort. One last question: Should I write this using C++09 variadic templates or the standard boost preprocessor techniques? I think that code written for variadic templates is more easily convertible to the preprocessor than vice versa, but I don't know. Thanks for your comments! Sean Hunt

2 1

1.35] Please remove \libs\filesystem\src\exception.cpp.
by Joe Gottman 31 Mar '08

31 Mar '08

Instead of using bjam, I compile the boost libraries on my own. I recently tried to compile the new version of boost::filesystem, and failed with exception.cpp. I had a scary few minutes until I realized I no longer needed this file since filesystem now uses errors from the system library. With header files, especially ones that the user never uses directly, there is no problem with leaving them in the directory after they are no longer needed, since they will never be included. However, users generally expect to have to compile source files, and so one that is included but no longer valid can cause major problems for people who compile without using bjam. Therefore, I would appreciate it if you would remove \libs\filesystem\src\exception.cpp. Joe Gottman

1 0

Re: [boost] Review Request: Generalization of the Pimpl idiom
by Vladimir.Batov＠wrsa.com.au 31 Mar '08

31 Mar '08

"vicente.botet" <vicente.botet(a)wanadoo.fr> wrote in message news:<014201c8937c$c1380180$0301a8c0@viboes1>... > Hello, > > First of all, I think that a pimpl library should have a place in boost, but > I think that the pimpl idiom do not scale very well (see below). > > Even if your library is usable in simple cases, I would like to see how it > can manage more complex cases. And if no satisfactory solution to this case > is possible, that the library states explicitly when it can not be used. Would it be possible to elaborate that exactly you mean by "more complex cases"? Inheriting from a pimpl-based class? I think it covered. What else? Not like my own deployment experience is of any guidance but still I've been using this idiom in my every-day development for about a year and have not come across something that I felt was not a good fit for that idiom. I'd rather say that the pimpl idiom in general does not handle well simple (rather than complex) cases where the overhead of creating private implementation on the heap is not affordable. > > Do you think to write the library documentation before the review? Even if > there is a tutorial in DDJ, IMHO, you should spend some time on the > documentation of the library before the review. In addition to the tutorial I have API documented in the header in the format for doxygen. Although I have to confess when I did run it through doxygen it did not seem to produce anything I saw valuable so I did not include that doxygen-generated file. Will look into it again though. Thanks, Vladimir.

1 0

Re: [boost] GSoC Ideas
by Cristianno Martins 31 Mar '08

31 Mar '08

Thanks for comments and advices, Doug. I really appreciate it. On Sun, 2008-03-30 at 21:14 -0300, Cristianno Martins wrote: > I'm Cristianno Martins, I'm starting master degree at State University of > Campinas (Brazil), and I'm very interested in participate of a Google Summer > of Code Project. Welcome! > This is the first time that I'm intending to develop some open source code. > There are many projects listed in GSoC home page, and I almost read all of > them, choosing two or three to write a propose. Usually, it is best to focus your energy on a single project that you're very interested in. Take the time to write a detailed proposal for that project to give it the best chance of success. > So, I really liked two ideas between the boost potential projects: > - safe integer -> basically, a creation of a template class to safely access > values in the memory; > - parallelizing Boost.Math -> using OpenMP to enable the source of > Boost.Math to run in multicore systems. > > I actually believe that I can do anyone of them, and I wanna propose a > project to each one. I only needed to know if anything is being done about > some of those. I also wanna know if someone have ideas to be done in these > projects and aren't listed at the Boost projects list. We often receive several applications for projects listed on the Boost projects list. That's why it is best to write a solid proposal that makes you stand out. - Doug -- Cristianno Martins Mastering in Computer Science State University of Campinas cristianno.martins(a)students.ic.unicamp.br skype:cristiannomartins g-Talk: cristiannomartins msn: cristiannomartins(a)hotmail.com

1 0

[serialization][1.36] ktmap contains extended_type_info with m_key == 0
by Felipe Magno de Almeida 31 Mar '08

31 Mar '08

Hi Robert, I'm hitting a assertion with m_key == 0. With my debugger I can find lots and lots of items with m_key == 0. None are one of my types, there are shared_ptr_1_32 with m_key == 0 and others. Do you have a newer 1.36 version? Am I doing something wrong? I'm using the 1.36 version for use with DLLs (export in a DLL and serialize/deserialize in another). Thanks, -- Felipe Magno de Almeida

3 18

[GSoC 2008] Deadline for student applications extended
by Hartmut Kaiser 31 Mar '08

31 Mar '08

FYI... > Hello everyone, > > This year, we experimented with the program timeline providing one > week for students to discuss project ideas with their mentors and then > a single week to submit applications. We have heard feedback from the > community that it would be beneficial to provide more time for > students to submit their applications, so we've done just that. > > > The new deadline for student applications is Monday, April 7, 2008. > > > For full details, you can check out the program timeline. Please note > that our engineers are working on the required updates to both > http://code.google.com/soc/2008/ and the FAQs to reflect the extended > deadline, and we will post to this list when the changes have gone > live. > > > In the meantime, get those applications in and nag your friends to > apply. :) > > > Cheers, > LH > > > Leslie Hawthorn > Program Manager - Open Source > Google Inc. > > > http://code.google.com/opensource/

1 0