- Boost-users - lists.boost.org

[program options] making options lower case???
by Ovanes Markarian 09 Jul '07

09 Jul '07

Hello! is there any chance to make some specific option values being lower case? With Kind Regards, Ovanes

1 0

Problem message bis
by question boost 09 Jul '07

09 Jul '07

Hi, using Code Blocks i got the following message: ld.exe "Cannot find -lboost_filesystem-mgw-mt-s-l_33_l" Then I do: cd C:\Documents and Settings\Administrateur\Bureau\boost_1_34_0\boost_1_34_0\tools\jam\src then C:\Documents and Settings\Administrateur\Bureau\boost_1_34_0\boost_1_34_0\tools\jam\src\build.bat Then I set the following variables: BOOST_ROOT= C:\Documents and Settings\src\boost and BOOST_BUILD_PATH=C:\Documents and Settings\src\boost\tools\build\v2. I don't know what to do now. It's a question like the other questions, so thank you for your response. _________________________________________________________________ David Guetta a réuni les sons les plus connus de Messenger dans le Mix Messenger, le son de l’été ! Téléchargez-le gratuitement ! http://specials.divertissements.fr.msn.com/mixmessenger

2 1

Réf. : [boost] Réf. : Re: [filesystem] building for cygwin
by frederic.bron＠alcan.com 09 Jul '07

09 Jul '07

Finally, I had a close look inside filesystem files and I discovered that to compile for cygwin 2 flags must be set: BOOST_POSIX_API and BOOST_POSIX_PATH! If only BOOST_POSIX_API, BOOST_WINDOWS_PATH is set automatically. Why??? This is a strange behaviour. Then: - either change the doc and add that for cygwin compilation, BOOST_POSIX_PATH must be set as BOOST_POSIX_API, - or change filesystem/config.hpp so that BOOST_POSIX_PATH is automatically set when BOOST_POSIX_API is set (I would prefer this solution). Regards, F. Bron frederic.bron@alca n.com Pour : boost(a)lists.boost.org Envoyé par : cc : (ccc : Frederic Bron/Alcan) boost-bounces@list Objet : [boost] Réf. : Re: [filesystem] building for cygwin s.boost.org 08/07/2007 19:32 Veuillez répondre à boost My problem is that I compiled 1.34.0 with -DBOOST_POSIX_API and it did not produce what it was suppose to produce, i.e. posix paths. F. Bron Lewis Hyatt <lhyatt@princeton. Pour : boost(a)lists.boost.org edu> cc : (ccc : Frederic Bron/Alcan) Envoyé par : Objet : Re: [boost] [filesystem] building for cygwin boost-bounces@list s.boost.org 08/07/2007 18:34 Veuillez répondre à boost I know it's possible because the cygwin package maintainer for boost re-compiled the boost 1.33.1 package for me a while ago to include -DBOOST_POSIX_API, to get the expected behavior on cygwin. If you post this to the cygwin mailing list (you can get at http://news.gmane.org/gmane.os.cygwin/ if you don't want to subscribe to the mailing list), I'm sure he can help you out. -Lewis frederic.bron(a)alcan.com wrote: > Maybe the developpers list can help? I try to have the POSIX behaviour under cygwin but get only the windows behaviour even if I compile the library and program with -DBOOST_POSIX_API. > What should I do? > > Regards > > F. Bron > > > frederic.bron(a)alcan.com > Envoyé par : Pour : boost-users(a)lists.boost.org > boost-users-bounces@list cc : (ccc : Frederic Bron/Alcan) > s.boost.org Objet : [Boost-users] Réf. : [filesystem] building for cygwin > > > 07/07/2007 15:13 > Veuillez répondre à > boost-users > > > > > > > > Unbelievable! It does not work anymore!!! I have rebuild again the library to be sure that g++ received well -DBOOST_POSIX_API and it does. > However, here is the output of the small program printed below: > > $ g++ -DBOOST_POSIX_API -I/cygdrive/d/Softs/boost_cyg/include -o toto toto.cc /cygdrive/d/Softs/boost_cyg/lib/libboost_filesystem.a > $ ./toto > ..\toto\x.xml > \cygdrive\d\toto\x.xml > > should be > ../toto/x.xml > /cygdrive/d/toto/x.xml > > What should I do? > > F. Bron > > #include <iostream> > #include <boost/filesystem.hpp> > > namespace fs=boost::filesystem ; > > int main() { > fs::path x("../toto/x.xml") ; > std::cout << x.file_string() << std::endl ; > fs::path y("/cygdrive/d/toto/x.xml") ; > std::cout << y.file_string() << std::endl ; > return 0 ; > } > > Avis : > Ce message et toute pièce jointe sont la propriété d'Alcan et sont destinés seulement aux personnes ou à l'entité à qui le message est adressé. Si vous avez reçu ce message par erreur, veuillez le > détruire et en aviser l'expéditeur par courriel. Si vous n'êtes pas le destinataire du message, vous n'êtes pas autorisé à utiliser, à copier ou à divulguer le contenu du message ou ses pièces jointes > en tout ou en partie. > > Notice: > This message and any attachments are the property of Alcan and are intended solely for the named recipients or entity to whom this message is addressed. If you have received this message in error > please inform the sender via e-mail and destroy the message. If you are not the intended recipient you are not allowed to use, copy or disclose the contents or attachments in whole or in part. > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost > _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Problem message
by question boost 09 Jul '07

09 Jul '07

Hi, using Code Blocks i got the following message: ld.exe "Cannot find -lboost_filesystem-mgw-mt-s-l_33_l" Then: cd C:\Documents and Settings\Administrateur\Bureau\boost_1_34_0\boost_1_34_0\tools\jam\src then.\\build.bat. Then I set the following variables: BOOST_ROOT= C:\Documents and Settings\src\boost and BOOST_BUILD_PATH=C:\Documents and Settings\src\boost\tools\build\v2. I don't know what to do now. So what must I do now in order not to get the message any more? Be clear. Thank You _________________________________________________________________ Le blog Messenger de Michel, candidat de la Nouvelle Star : analyse, news, coulisses… A découvrir ! http://michel-nouvelle-star2007.spaces.live.com/

1 0

[mpi] shared_ptr + packed_iarchive
by Andras Joo 09 Jul '07

09 Jul '07

Dear All, I'm facing the following problem. I have the following class hierarchy: AbstractBase <--- AbstractDerived <---- ConcreteDerived I managed to make the serialization of shared_ptr<AbstractBase> using text and binary archives (text_[i/o]archive, binary_[i/o]archive), tested, and works fine. However, when I try to send an shared_ptr<AbstractBase> with some MPI function, the compiler complains about packed_iarchive not having append() and reset() functions. /home/jooam/usr/include/boost-1_35/boost/serialization/shared_ptr.hpp:129: error: 'class boost::mpi::packed_iarchive' has no member named 'append' /home/jooam/usr/include/boost-1_35/boost/serialization/shared_ptr.hpp:137: error: 'class boost::mpi::packed_iarchive' has no member named 'reset' Any help is appreciated. Thank you, Andras ____________________________________________________________________________________ Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center. http://autos.yahoo.com/green_center/

3 3

Can't compile my project with Boost 1.3.3.1 & stlport
by Hongquan 09 Jul '07

09 Jul '07

Hi Everyone: I use boost 1.3.3.1 and stlport in my project,actually Boost::regex is my need. If I compile my project without include boost files in project settings,it's ok and of course cl told me that it can't find some header files such as regex.hpp . But if I add boost path into my project settings,the compiler will threw some erro just like below: BoostRegHandler.cpp D:\SyncSdk\include/stlport\cstddef(35) : fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'msc1.cpp', line 1794) Please choose the Technical Support command on the Visual C++ Help menu, or open the Technical Support help file for more information Error executing cl.exe. I have no idea on this,does anyone compile your project with boost & stlport successfully? Or is there any seetings error of my project. BTW:I use vc6.0 , XP proffessional ,Intel P4 2.0 512 RAM Hongquan

1 0

[serialization] minor comment error
by Sean Cavanaugh 09 Jul '07

09 Jul '07

In basic_binary_oarchive.hpp there exists a comment which is obviously the result of an uncorrected cut-and-paste (it looks like the comment just needs to be deleted) ///////////////////////////////////////////////////////////////////////// // class basic_text_iarchive - read serialized objects from a input text stream template<class Archive> class basic_binary_oarchive : public detail::common_oarchive<Archive>

1 0

Re: [Boost-users] [serialization] hacking serialization : handles to pointers
by Sean Cavanaugh 08 Jul '07

08 Jul '07

On 7/8/07, Robert Ramey <ramey(a)rrsd.com> wrote: > > Sean Cavanaugh wrote: > > Ok I've spent a good chunk of my day making a set of custom archive > > class, based on the portable_binary_iarchive and > > portable_binary_oarchive. > > > > > > I have a non-virtual class hierarchy named Asset, in memory this is a > > cyclic graph, but my requirements are that this structure cannot be > > serialized all at once, it has to be broken up at boundaries. So > > the archiver serializes the first Asset* (which is always the root > > object passed into operator&). This object serializes as normally as > > per the boost serialization code, except except that when subsequent > > Asset*'s are encountered > > > > ?which point to a previously serialized object? or any subsequent > > Asset *? > > > > I send the pointer into an AssetManager class and translate the > > Asset* into a ResourceID, and serialize the ResourceID instead of the > > object. This is done by directly calling operator& inside > > save_override. > > > ******* > Hmmm this sounds to me exactly equivalent to what the serialization > system does by default for tracked objects. Objects serialized > through pointers are tracked by default. Your "ResourceID" seems a > re-implemenation of the "object id" used by the serialization libary > to track This is true, but the serialization libraries view of the id's only have archive scope, which means the same id's are used for totally different things when you use multiple archives. My ResourceID's have to be globally unique, in the sense they are GUIDs or relative pathnames, which can then be mapped to a fully qualified pathname and can be loaded on demand. As far as the archive class is concerned its a user defined translation (proxy-to-real and real-to-proxy) that exists for certain types. So in this case its conceptually an archive of archives. With the outermost archive being the filesystem, and the innermost being a single object (a file). The file only contains one object, and all links to other objects are handles (a filename). So the innermost code when it is loading from the filesystem, it knows that it wants a pointer to another object, but it only has its name. So it has to ask the filesystem class to translate the name into an object, which it can do because it can lookup if its already loaded and return that, or literally open another file based archive and read it in on demand, and return that. The archive class doesn't care about the specifics really, it just needs the means to achieve the result. So the archive's base class code should be doing this in a conceptual way: for_each type X, if has_user_defined_translation<X*> implement : on_save -> translate type X* to type ProxyX via a function : ProxyX RealToProxy(X* x), serialize the ProxyX on_load -> read ProxyX translate to X*, via a function : X* ProxyToReal(ProxyX& px), return the X* Except that this on_save and on_load example needs to have yet another template argument, on whether the first occurence of X should be literally saved or not, since we might be saving a hierarchy of Bar's that always save handles to Foo's at all times. > > > ... > > > > I also have to hard-code the full list of derived Asset types and > > manually provide specializations for all of them in save_override and > > load_override. > > > **** > Well, since they're different - I would expect each of them to have a > different serialize function. If all the serialize functions are the > same, it would seem that something should be moved from the derived > class to the base class. > > > > If I use the base class, I end up slicing my class down to its base, > > and cannot serialize it. > > > **** > serializing through a base class pointer solves this problem as well. In my currently kind-of-working hacked up version of the archive classes the methods load_override are nearly identical when specializing for AssetModel, AssetTexture, etc. The behavior is constant (proxy-to-real translation or vice-versa) but the type is not. I can slice them here safely on saving, but not on loading (since the C++ code in the serialize method 'ar & foo', is expecting a more-derived type to be filled in). > I can't make serialize virtual, since the intrusive serialize methods > > are templates, but it certainly would solve the problem if it were > > possible. > > *** > I suspect that if the other changes suggested were implemented this > would disappear as a problem. I don't think I've tried it, but > rather than including boiler plate code in each derived class, one > might try adding a "mix-in" base class which contains the serialize > function. I'll play around with alternatives, I basically spent the day learning the archive templates by watching the code flow. > > > In addition the bodies of all of my overrides are completely > > identical except for the classname (AssetModel, AssetTexture, etc). > > > > Which means I'll be wrapping the bodies of a generic save_override > > and load_override in a macro, and have to manually add all Asset > > derived classes to a list of classes inside my archive class. Which > > means that my archiver cannot be generic, even though I have managed > > to make it a template in the sense that the passed in asset manager > > and base asset types are template parameters. > > > *** > looks to me that you've gotten off on the wrong foot and stuck with it. That isn't possible with learning new code :) This is what the path of least resistance yielded, with the docs and examples provided by boost. Basically this is as far as I got without having to directly hack on the existing boost code, and having to deal with a crash course on the code flow and internal data structure of everything. > > > *** me this is exactly the wrong approach. Now you've coupled your > classes > to be serialized to a specific archive. This means you won't be able to > use > any other archive type and you've defeated one of the main benefits to the > serialization library. Perhaps it wasn't a suitable library for your > task. The library can do what I want, because I have the source code :) Anyway the classes aren't coupled to the archive with what I've come up with so far, its the other way around. I definitely do not want my classes to understand archiving beyond a very basic sense of having to call operator& on most of their fields, since I plan on having several wildly different archive classes calling the serialize methods on my classes. So I have a working implementation, how do I make it better? > > **** > Maybe you might try doing it in the simplest way. > > I can't see how what you want to do is different than what everyone else > uses the library for. And I can't see how what you want to do is > different > than what the examples do. > > I could get the behavior I want by altering the serialize methods, but then it would be ill formed for other archives. I could also template specialize the serialize methods for the archive in question, but then I would have to write more than one. Its the archives job to interpret what to do when you call ar & foo. I anticipate having more data than I can load, so I need to load and save at an object level. But I still need to write the serialize methods as if they all could fit in memory, since I plan on having other archive classes that do operate on the graph of what is loaded at runtime (i.e. to compute garbage collection). In essence the archive classes need to be made to be programmable for these behaviors to work: Graph of Foo: Saving: save the first Foo*, translate all further Foo*'s into a user defined handle with a user defined function and save that instead. Loading: load the first Foo*, assume all further Foo*'s are saved with a user defined handle, translate them back into live objects on demand, and also use the existing caching scheme to prevent having to translate the same user-defined handle over and over. Graph of Bar: Saving: save all Bar's, but save all occurences of Foo*'s as handles Loading: save all Bar's, but load all occurences of Foo*'s from handles Garbage Collecting Foo: 'Saving' : archive an array of live root level Foo objects, build a list of all Foo* that are reachable through serialization. Compare this list to the full list of Foo objects, and unload the ones that are missing.

1 0

How to use boost iostream with zlib
by Meryl Silverburgh 08 Jul '07

08 Jul '07

Hi, Can you please tell me how can I use boost iostream with zlib to inflate an byte stream? Where can I find an example? Thank you.

4 12

non-boost: project idea help. Java expert apperciated.
by chun ping wang 08 Jul '07

08 Jul '07

Dear boost community. Right now I am planning on doing somewhat of a mock boost for java. http://cs.calstatela.edu/wiki/index.php/Current_MS_Students/Chun_ping_Wang. I am not going to use the name boost but i want to know a.) a good name for it. b.) five common non-ui files you think Java needs that it is missing. All implementation can be done using low level arrays and iterators (if needed). Thanks

1 0