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

Boost under Windows
by Umut TABAK 11 Jun '06

11 Jun '06

Dear all, Can somebody provide the detailed steps to build and set up boost running under Windows for MSVC. I have used boost under Linux(Ubuntu) where the installation is just an easy apt-get there. But I could not do it under Windows. I tried the steps in the getting started guide. But I think I missed something so your help is very much appreciated. Best Regards, Umut

2 1

[shmem-interprocess] Shmem 0.93 and update on Interprocess
by Ion Gaztañaga 10 Jun '06

10 Jun '06

Hi to all, I've just uploaded to Boost Vault a new Shmem bugfix version (0.93) with bugfixes to make Shmem MinGw friendly (props to Jan Stetka). Library and documentation download: http://boost-consulting.com/vault/index.php?&direction=0&order=&directory=M… Online documentation: http://ice.prohosting.com/newfunk/boost/libs/shmem/ //////////////////////////////////////////////////////////// Update on Interprocess: -> Due to Shmem problems with shared memory/named mutex/name semaphore lifetime between POSIX/Windows. I've decided to change Shmem approach (emulation of Windows lifetime behavior in POSIX with reference counting) to a POSIX lifetime (explicit unlinking shared memory). This means that I have to rework all main classes to achieve POSIX persistence semantics in Windows even when a process crashes. This will require using memory mapped files to emulate shared memory (with some tricks to avoid performance problems with file-memory synchronization if it's possible). I think that this approach will be much more portable than the Shmem approach. -> I'm also experimenting with a new allocator with expand-in place capabilities to allow realloc-like features in shared memory containers. The first results are encouraging both in size savings and speed improvements. This expand in place features are based on a paper I plan to present as a ISO C++ proposal based on N1953. You can find the current draft here, if you want to make some comments: http://ice.prohosting.com/newfunk/proposals/nXXXX%20Improving%20STL%20Alloc… -> I'm also experimenting with a new reduced mutex interface (basically condensing shared_mutex, shared_try_mutex and shared_timed_mutex in a single interprocess_mutex type. Something in the line of the draft "Simplifying And Extending Mutex and Scoped Lock Types For C++ Multi-Threading Library" that you can find here: http://ice.prohosting.com/newfunk/proposals/ I'm also trying to implement a process-shared version of Howard Hinnant's upgradable_mutex class described here: http://home.twcny.rr.com/hinnant/cpp_extensions/rw_perf.html http://home.twcny.rr.com/hinnant/cpp_extensions/threads_move.html I still have some bugs in my upgradable_mutex implementation that I plan to solve soon. I think that this enhazed rw mutex is a winner for Interprocess. -> I'm adding a new mutex type: file_lock. The classic UNIX fcntl / Windows FileLockEx file locking is an interesting addition to Interprocess since both in POSIX and Windows, the lock is automatically unlocked by the OS when the process ends/crashes. This can help problematic Shmem atomic creation+initialization functions if the process crashes executing the atomic code. File locking is also many times easier to use than named mutexes or shared memory + process shared mutexes, specially for simple locking. That's all. Thanks for your patience! Regards, Ion

1 0

[Boost.Python] Extracting indirect base.
by Sebastian Redl 10 Jun '06

10 Jun '06

(No luck on C++-sig - is that list even active? There's absolutely no traffic, not one mail in two days. Anyway, trying again here.) Hi, I've got a hand-wrapped plugin interface hierarchy for my program allowing implementing plugins in Python. This looks approximately like this: class Plugin { public: virtual void init() = 0; virtual PluginCategory getCategory() = 0; // Subtype of the plugin // ... }; class InputPlugin : public Plugin { public: virtual void loadData(const string &resource, DataBag &target) = 0; }; class OutputPlugin : public Plugin { public: virtual void saveData(const string &resource, const DataBag &source) = 0; }; These are the plugin interfaces. PluginCategory is an enum identifying the concrete subtype of the plugin, i.e. either Input or Output. I've got them wrapped like this: class PluginWrap : public Plugin, public boost::python::wrapper<Plugin> { virtual void init() { this->get_override("init")(); } // ... }; class InputPlugin : public InputPlugin, public boost::python::wrapper<InputPlugin> { virtual void loadData(...) { ... } }; // ... BOOST_PYTHON_MODULE(myprogram) { class_<PluginWrap, boost::noncopyable>("Plugin") .def("init", pure_virtual(&Plugin::init)) .def( ... ) ; class_<InputPluginWrap, bases<PluginWrap>, boost::noncopyable>("InputPlugin") .def("loadData", ...) ; // ... } A plugin file looks like this: from myprogram import * class SomePlugin(InputPlugin): def init(self): // ... // ... plugins = [SomePlugin()] I then attempt to load these modules like this: PythonLoader::load(const path &file) { // Parse file and get namespace object for it. Get the "plugins" list and extract a python::list. Get the length of that list. python::list plugs = ...; int len = // get length of plugs for(int i = 0; i < len; ++i) { try { py::object plug = plugs[i]; Plugin *plugin = py::extract<Plugin *>(plug); // <------------- plugins.push_back(plugin); } catch(py::error_already_set &e) { // handle error } } } Finally, my problem: the extract<Plugin*> call fails: TypeError: No registered converter was able to extract a C++ pointer to type Plugin from this Python object of type SomePlugin So here are my questions: 1) Is this expected behaviour? Does my wrapping not register the appropriate base pointer extractors? 2) How can I manually register appropriate converters? 3) If 2 is not possible, how can I work around the problem? Thanks in advance Sebastian Redl

1 0

BJAM : tracking dependencies
by __PPS__ 10 Jun '06

10 Jun '06

Hello ppl I have some questions about the way bjam implements dependencies tracking. I need a tool that would do this for a project that uses gcc. (it doesn't use gmake and not entire gnu toolset is available) does bjam by iteself parses all the source files, looking for incldues and then parses them to see any updates, or gcc does it? by the way I downloaded bjam sources and wanted to build it and on one machine it gave me absolutely weird results (compilation went fine, but on linking I saw some strange output with strings from registry): ... Compiling... order.c Generating Code... Microsoft (R) Incremental Linker Version 8.00.50727.42 Copyright (C) Microsoft Corporation. All rights reserved. [HKEY_CLASSES_ROOT\Directory\shell\Command Prompt Here] Settings\Temp\deleteme.r eg "@=Command &Prompt Here" Settings\Temp\deleteme.reg [HKEY_CLASSES_ROOT\Directory\shell\Command Prompt Here\command] Settings\Temp\de leteme.reg "@=cmd.exe /k cd %1 " Settings\Temp\deleteme.reg LINK : fatal error LNK1181: cannot open input file '[HKEY_CLASSES_ROOT\Directory \shell\Command.obj' C:\PAVEL\gnu_tools\tools\build\jam_src> Same shit happend with vs71

2 1

Re: [Boost-users] Help with Tokenizer
by David Klein 09 Jun '06

09 Jun '06

boost-users-bounces(a)lists.boost.org wrote: > I have a string that is delimited with '|' that I want to > parse with boost::tokenizer. > > ie: "label 1|label2||label 3" > > It all parses ok except that the whitespace within the label > is removed. > > Is there a way to configure the tokenizer to leave whitespace alone? > > Thanks > Frank > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users hi frank, the following snippet works for me (winxp, vc71, boost 1.33.1): typedef boost::char_separator<char> separator_type; string s("label 1|label2||label 3"); boost::tokenizer<separator_type> t(s, separator_type("|")); copy(t.begin(), t.end(), ostream_iterator<string>(cout, "\n")); output: label 1 label2 label 3 HTH dave

2 1

Help with Tokenizer
by Frank 09 Jun '06

09 Jun '06

I have a string that is delimited with '|' that I want to parse with boost::tokenizer. ie: "label 1|label2||label 3" It all parses ok except that the whitespace within the label is removed. Is there a way to configure the tokenizer to leave whitespace alone? Thanks Frank

2 2

[test] BOOST_CHECK_NOT_EQUAL?
by Ed Johnson 09 Jun '06

09 Jun '06

Hi, Is there a way to get the funcationality of BOOST_CHECK_EQUAL when I want to test that two parameters are not equal to each other? I like the way BOOST_CHECK_EQUAL allow me to see the mismatched runtime values. I have been creating a custom message for BOOST_CHECK_MESSAGE to achieve this functionality, but it would be nicer if there was an automated way to do it. Thanks, Ed Johnson

4 11

[Review][PQS] Review ends
by fred bertsch 09 Jun '06

09 Jun '06

Hello, boosters! Any given day exists for 50 hours, but it does end at some point. Likewise, the PQS review ends at some point. I will arbitrarily say midnight UTC and the timezone of the author. However, it will take me roughly a week to collate all of the reviews and reach an official decision, so don't feel shy about posting or mailing me additional reviews. I thank the reviewers very much for reviewing the library, and I thank Andy Little even more for all of his work responding to the reviews and for writing the library in the first place! -Fred Bertsch

1 0

Problem with serialization of shared_ptr (with example code)
by Tim Taylor 09 Jun '06

09 Jun '06

Hi, I am having some troubles with serialization of shared_ptrs. The basic problem is that when I serialize a shared_ptr, then later deserialize into a new shared_ptr, the use_count of the new pointer is, incorrectly (as far as I can see), 2 rather than 1. I am using boost 1.33.1 and gcc 4.0.1. Here is some example code to demonstrate the problem: ----- // compile with: // gcc -o ptrser-test ptrser-test.cpp -lstdc++ -lboost_serialization-gcc #include <iostream> #include <fstream> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/shared_ptr.hpp> using namespace std; using namespace boost; class Item { public: // Constructors/destructor-------------------------- Item(int n = 0) : _n(n) { cout << "In Item constructor" << endl; }; Item(const Item& other) { cout << "In Item copy constructor" << endl; _n = other._n; }; ~Item() { cout << "In Item destructor" << endl; }; // Data members------------------------------------- int _n; // Methods------------------------------------------ friend class boost::serialization::access; template<class Archive> void serialize(Archive& ar, const unsigned int version) { ar & _n; } }; class Bag { public: // Constructors/destructor-------------------------- Bag() { cout << "In Bag default constructor" << endl; }; Bag(shared_ptr<Item> item) : _item(item) { cout << "In Bag shared_ptr constructor" << endl; }; Bag(const Bag& other) { cout << "In Bag copy constructor" << endl; _item = other._item; }; ~Bag() { cout << "In Bag destructor" << endl; }; // Data members------------------------------------- shared_ptr<Item> _item; // Methods------------------------------------------ void printUseCount() const { cout << "Use count: " << _item.use_count() << endl; } friend class boost::serialization::access; template<class Archive> void serialize(Archive& ar, const unsigned int version) { ar & _item; } }; int main(int argc, char **argv) { const char *filename = "bag.ser"; // create a Bag object with a new Item in it Bag *pBag = new Bag(shared_ptr<Item>(new Item(1))); // now serialize the Bag cout << "About to serialize bag..." << endl; ofstream osSer(filename); boost::archive::text_oarchive oa(osSer); const Bag& constBag = *pBag; oa << constBag; osSer.close(); pBag->printUseCount(); // delete the original Bag cout << "About to delete bag 1..." << endl; delete pBag; // create a new Bag object cout << "About to create a new bag..." << endl; pBag = new Bag; pBag->printUseCount(); // and deserialize it into the new Bag object cout << "About to deserialize bag..." << endl; ifstream isSer(filename, std::ios::binary); boost::archive::text_iarchive ia(isSer); ia >> *pBag; isSer.close(); pBag->printUseCount(); // delete the second BSag cout << "About to delete bag 2..." << endl; delete pBag; return 0; } ----- This code produces the following output: ----- In Item constructor In Bag shared_ptr constructor About to serialize bag... Use count: 1 About to delete bag 1... In Bag destructor In Item destructor About to create a new bag... In Bag default constructor Use count: 0 About to deserialize bag... In Item constructor Use count: 2 About to delete bag 2... In Bag destructor In Item destructor ----- The series of constructor and destructor calls is as expected. After the first Bag object is created with a shared_ptr to an Item in it, the use_count of the shared_ptr is 1. When the first Bag object (including the shared_ptr) are deleted, and a new, empty Bag object created, the use_count is now (as expected) 0. However, when the serialization archive is deserialized into the new Bag object, the use_count of the shared_ptr jumps from 0 to 2. Am I doing something silly here, or is this a bug in the shared_ptr serialization code? For interest, the saved archive (bag.ser) produced by this code looks like this: ----- 22 serialization::archive 3 0 0 0 1 2 1 0 0 1 ----- Any help would be much appreciated. Tim

3 3

[Review][PQS] Physical Quantities System review (May 31 through June 9)
by fred bertsch 09 Jun '06

09 Jun '06

The review of Andy Little's Physical Quantities System begins today, May 31, 2006, and continues through June 9, 2006. Download: pqs_3_1_0 is the Official Boost Review version of pqs. (Please note that pqs_3_1_0 has a bug in one header. This can be either patched according to the latest release notes, "relnotes.txt" available from http://tinyurl.com/7m5l8 or alternatively download pqs_3_1_1, which is basically equivalent to pqs_3_1_0, except the bug has been fixed there. Description PQS (Physical Quantities System) is designed to replace the use of floating point types for modelling physical quantities in C++ programs. Advantages include automated dimensional analysis checking, automatic unit conversions, self documentation of code and uniform mechanisms for dealing with physical quantities overall, allowing better interoperability, accuracy and repeatability among engineering, physics and trade applications. The library will ultimately consist of various types for modelling quantities in different situations. The t1_quantity, which is the first to be implemented, performs all its dimensional analysis checks as well as parts of its unit conversion calculations, at compile time rather than runtime, for maximum efficiency. PQS is designed with a firm commitment to the SI system, as being the internationally agreed preferred system of units. A reasonable selection of common quantities and units is included in the review version for demonstration purposes. The intent is to expand on this to include all the common quantities mentioned in Appendix B.8 and B.9 of the NIST SI document: http://physics.nist.gov/cuu/pdf/sp811.pdf The library also defines a selection of physical constants again intended as a flavour of the constants that would be included in a full library implementation as outlined in: http://physics.nist.gov/cuu/pdf/chart1.pdf Review questions: Please always explicitly state in your review, whether you think the library should be accepted into Boost. You might want to comment on the following questions: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? -Fred Bertsch

4 4