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

Re: [Boost-users] [Test] Running individual test cases
by Sohail Somani 17 Jul '06

17 Jul '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Gennadiy Rozental > Sent: Monday, July 17, 2006 9:31 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] [Test] Running individual test cases > > > "Sohail Somani" <s.somani(a)fincad.com> wrote in message > news:1C1EBEF8DBACDC439D038EA051674EC735B941@xbox.financialcad.com... > > Hi, > > > > I recall a thread about running individual test cases by name. Might > > even have been yesterday. Anyway, I'd like to put in a "me > too" vote for > > that and also ask what I can currently do to continue using the auto > > registration capability but perhaps modify it to only > register certain > > functions? Would I need to create my own test suite? > > I could always use compile time switches This *could* work, but imho it really prevents the quick turn around you need when debugging unit tests. I personally would prefer the test runner to by default run all tests and given a bunch of --run_test=test1 --run_test=test2 command line arguments, it runs only those tests. If you could tell me what to read or change to get the framework to do this, I'd be happy. Thanks Sohail

2 1

Boost Test usage
by Matt Schuckmann 17 Jul '06

17 Jul '06

I've been looking into using the boost test library to start testing some of our code and it looks pretty good. I've gone through the documentation and several of the examples and there are a couple of things I don't really get I don't see how the test_suite class lets you create do anything special with regards to building multi-level tests, none of the examples really show multilevel test hierarchy and how it really helps me. It looks like it's really just a way of using a class to group test functions instead of a series of free functions, am I missing something here? I really expected more from a feature like this, I'm thinking of things like Command line control over which test suites to run, I mean you name the test suites but you don't appear to do anything with that name Reporting success and failure grouped by test suite Am I missing something here, is this stuff possible and the examples don't show it or are these feature that are yet to come or haven't been thought of? I don't see a good example for how I should setup a unit test for a real world type project you know an extensive example that covers inputs, outputs, multiple test suites, etc all in one example. In my case I've a got a library with several independent classes and functions that I'd like to test and I'm not sure if I should be creating multiple executables (1 for each test case) or a single executable that tests everything, I don't understand the pros and cons of either case. It seems like I want the single executable that can test everything or that can test just want I tell it to test. Any info would be appreciated. Matt S.

2 4

[Test] Running individual test cases
by Sohail Somani 17 Jul '06

17 Jul '06

Hi, I recall a thread about running individual test cases by name. Might even have been yesterday. Anyway, I'd like to put in a "me too" vote for that and also ask what I can currently do to continue using the auto registration capability but perhaps modify it to only register certain functions? Would I need to create my own test suite? By the way, boost test has been really great to me so far, its been very useful while testing my latest project. Keep up the good work! Thanks, Sohail

2 1

[thread] Keeping leak detectors still...
by Daniel Krügler 17 Jul '06

17 Jul '06

Hello!, Its a well-known issue, that Boost-Thread users on Windows machines have observed that popular leak reporting tools loudly notify a missing delete for the dynamically allocated mutex in tss_hooks.cpp. A good overview for this discussion can be found in: http://groups.google.de/group/boost-list/browse_thread/thread/f5788746e458d… While I don't want to heat up the discussion whether this is actually a "leak" or not, many code style guides of companies give very bad points on such behaviour, so I would like to ask whether it is possible to ensure a proper clean-up of this by code (before the system does), to keep those detector programs quiet... Simple question of a non-expert: Couldn't one simply change the current impl of on_process_exit in tss_hooks.cpp to extern "C" BOOST_THREAD_DECL void on_process_exit(void) { { // Wrap into scope boost::call_once(init_threadmon_mutex, once_init_threadmon_mutex); boost::mutex::scoped_lock lock(*threadmon_mutex); BOOST_ASSERT(attached_thread_count == 0); //Free the tls slot if one was allocated. if (tls_key != invalid_tls_key) { TlsFree(tls_key); tls_key = invalid_tls_key; } } delete threadmon_mutex; // Shouldn't that be the last point of access?? threadmon_mutex = 0; // For those who prefer a defined value... } OK, I see that the docs for this function says: "Must not be omitted; may be called multiple times." Question is: Does there exist at least the guarantee, that there is always the same number of on_process_enter and on_process_exit calls? If yes: Wouldn't a simply reference counting scheme using one of the atomic integer incrementing/decrementing functions (also provided by boost via interlocked.hpp) allow a thread-save deletion of that mutex object? Thanks for your patience, Daniel Krügler

2 6

[filesystem] Is it a bug or not
by Ovanes Markarian 17 Jul '06

17 Jul '06

Hi! On my Windows computer I have cygwin installed and it created the following file names in directory c:\ %backup%~ .emacs .emacs~ .tcltcinfo.txt The last file was created by some cygwin app. Now if I try to iterate through this directory: for(fs::directory_iterator dir_itr( full_path ), end_iter; dir_itr != end_iter; ++dir_itr) { try { if(!fs::is_directory(*dir_itr)) { std::pair<std::string, std::string> file_name( fs::basename(dir_itr->leaf()), fs::extension(dir_itr->leaf()) ); std::cout << "fname: " << file_name.first << ", extension: " << file_name.second << std::endl; } } catch(std::exception const& ex ) { std::cout << dir_itr->leaf() << " " << ex.what() << std::endl; } } Exceptions are thrown: %backup%~ boost::filesystem::path: invalid name "%backup%~" in path: "%backup%~" .emacs boost::filesystem::path: invalid name ".emacs" in path: ".emacs" .emacs~ boost::filesystem::path: invalid name ".emacs~" in path: ".emacs~" .tcltcinfo.txt boost::filesystem::path: invalid name ".tcltcinfo.txt" in path: ".tcltcinfo.txt" I know that it is impossible to create these file manually, but software is allowed to do this. Therefore I don't think these exceptions are correct. With Kind Regards, Ovanes Markarian

2 1

bjam w/ minggc g++-3.4.5-20060117: undefined reference
by Jeffrey Chang 17 Jul '06

17 Jul '06

Hi, I'm building boost_1_33_1 on mingw win32 environment via: boost-jam-3.1.3-1-ntx86/bjam.exe -sTOOLS=mingw stage Everything goes fine and most libraries are built and run without problems, except for link-time errors of "undefined references" for the following functions: "boost::filesystem::detail::system_error_code()" "boost::filesystem::filesystem_error::~filesystem_error()" "boost::filesystem::filesystem_error::filesystem_error(...)" "vtable for boost::filesystem::filesystem_error" "boost::archive::ARCHIVE_VERSION()" "boost::archive::ARCHIVE_SIGNATURE()" "boost::signals::trackable::signal_connected(...)" It seems some of the object files doesn't get picked up while building their corresponding libraries; for example, ARCHIVE_VERSION() and ARCHIVE_SIGNATURE() are defined in libs/serialization/src/basic_archive.cpp file, which are compiled correctly into basic_archive.obj, yet somehow the bjam link process cannot find it while building the Serialization library. If I inline the definition of ARCHIVE_VERSION() and ARCHIVE_SIGNATURE() into its declaration header file of boost/archive/basic_archive.hpp, the the Serialization library is built without problem. This shows that I'm probably missing something for the above build command. Also, in my mingw win32 build output of stage/lib directory, the corresponding libraries with the above "undefined references" (libboost_filesystem-mgw-*, libboost_serialization-mgt-*, and libboost_signals-mgw-*) are generated as a result of the above bjam build command, even though mingw's ld.exe doesn't recognize these lib files. Is this a bug in bjam logic? Here's my mingw win32 environment: * MSYS-1.0.11-2004.04.30-1 * msysDTK-1.0.1 * binutils-2.16.91-20060119-1 * gcc-core-3.4.5-20060117-1 * gcc-g++-3.4.5-20060117-1 * w32api-3.7 * mingw-runtime-3.10 * mingw-utils-0.3 Attached is the excerpt of above undefined reference errors. I'm not familiar with bjam; it'd be great if someone can shed lights on what's wrong. (please cc me as I'm not subscribed to the list) ------------- begin: bjam build output ------------ FileClone stage\lib\boost_date_time-mgw-mt-d-1_33_1.lib gcc-Link-action bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\debug\boost_filesystem-mgw-d-1_33_1.dll bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\debug\boost_filesystem-mgw-d-1_33_1.lib Creating library file: bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\debug\boost_filesystem-mgw-d-1_33_1.lib bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\debug\operations_posix_windows.obj: In function `ZN5boost10filesystem6detail12dir_itr_initERNS_10shared_ptrINS1_11dir_itr_impEEERKNS0_4pathE':c:/e2e/win32/ref/boost/boost_1_33_1/libs/filesystem/build/../src/operations_posix_windows.cpp:308: undefined reference to `boost::filesystem::detail::system_error_code()' :c:/e2e/win32/ref/boost/boost_1_33_1/libs/filesystem/build/../src/operations_posix_windows.cpp:308: undefined reference to `boost::filesystem::filesystem_error::filesystem_error(std::string const&, boost::filesystem::path const&, int)' :c:/e2e/win32/ref/boost/boost_1_33_1/libs/filesystem/build/../src/operations_posix_windows.cpp:308: undefined reference to `boost::filesystem::filesystem_error::~filesystem_error()' .... :c:/e2e/win32/ref/boost/boost_1_33_1/boost/iterator/iterator_facade.hpp:(.text$_ZN5boost10filesystem16filesys tem_errorC1ERKS1_[boost::filesystem::filesystem_error::filesystem_error(boost::filesystem::filesystem_error const&)]+0x4c): undefined reference to `vtable for boost::filesystem::filesystem_error' .... "g++" "-Wl,--enable-auto-image-base" "-Wl,--exclude-symbols,_bss_end__:_bss_start__:_data_end__:_data_start__" "-Wl,--out-implib,bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\release\threading-multi\boost_filesystem-mgw-mt-1_33_1.lib" -mthreads -s -shared -Wl,--allow-multiple-definition -mno-cygwin -o "bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\release\threading-multi\boost_filesystem-mgw-mt-1_33_1.dll" -L"" "bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\release\threading-multi\exception.obj" "bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\release\threading-multi\operations_posix_windows.obj" "bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\release\threading-multi\path_posix_windows.obj" "bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\release\threading-multi\convenience.obj" ...failed gcc-Link-action bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\release\threading-multi\boost_filesystem-mgw-mt-1_33_1.dll bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\release\threading-multi\boost_filesystem-mgw-mt-1_33_1.lib... ...removing bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\release\threading-multi\boost_filesystem-mgw-mt-1_33_1.lib ...skipped <@boost!lib>boost_filesystem-mgw-mt-1_33_1.dll for lack of <@boost!libs!filesystem!build\boost_filesystem.dll\mingw\release\threading-multi>boost_filesystem-mgw-mt-1_33_1.dll... ...skipped <@boost!lib>boost_filesystem-mgw-mt-1_33_1.lib for lack of <@boost!libs!filesystem!build\boost_filesystem.dll\mingw\release\threading-multi>boost_filesystem-mgw-mt-1_33_1.lib... FileClone stage\lib\boost_program_options-mgw-d-1_33_1.lib FileClone stage\lib\boost_program_options-mgw-mt-d-1_33_1.lib FileClone stage\lib\boost_python-mgw-d-1_33_1.lib FileClone stage\lib\boost_python-mgw-mt-d-1_33_1.lib FileClone stage\lib\boost_python-mgw-1_33_1.lib FileClone stage\lib\boost_python-mgw-mt-1_33_1.lib FileClone stage\lib\boost_regex-mgw-d-1_33_1.lib FileClone stage\lib\boost_regex-mgw-mt-d-1_33_1.lib FileClone stage\lib\boost_regex-mgw-1_33_1.lib gcc-Link-action bin\boost\libs\serialization\build\boost_serialization.dll\mingw\debug\boost_serialization-mgw-d-1_33_1.dll bin\boost\libs\serialization\build\boost_serialization.dll\mingw\debug\boost_serialization-mgw-d-1_33_1.lib Creating library file: bin\boost\libs\serialization\build\boost_serialization.dll\mingw\debug\boost_serialization-mgw-d-1_33_1.lib bin\boost\libs\serialization\build\boost_serialization.dll\mingw\debug\basic_iarchive.obj: In function `ZSt38__copy_backward_output_normal_iteratorIPN5boost7archive6detail19basic_iarchive_impl10cobject_idEN9__gnu_cxx17__normal_iteratorIS5_St6vectorIS4_SaIS4_EEEEET0_T_SD_SC_11__true_type':c:/e2e/win32/ref/boost/boost_1_33_1/libs/serialization/build/../src/basic_iarchive.cpp:(.text$_ZN5boost7archive6detail19basic_iarchive_implC1Ej[boost::archive::detail::basic_iarchive_impl::basic_iarchive_impl(unsigned int)]+0x52): undefined reference to `boost::archive::ARCHIVE_VERSION()' ..... ' bin\boost\libs\serialization\build\boost_serialization.dll\mingw\debug\binary_iarchive.obj: In function `ZN5boost7archive20binary_iarchive_implINS0_15binary_iarchiveEE13load_overrideINS0_13tracking_typeEEEvRT_i':c:/e2e/win32/ref/boost/boost_1_33_1/boost/archive/binary_iarchive.hpp:(.text$_ZN5boost7archive21basic_binary_iarchiveINS0_15binary_iarchiveEE4initEv[boost::archive::basic_binary_iarchive<boost::archive::binary_iarchive>::init()]+0x6e): undefined reference to `boost::archive::ARCHIVE_SIGNATURE()' ..... "g++" "-Wl,--enable-auto-image-base" "-Wl,--exclude-symbols,_bss_end__:_bss_start__:_data_end__:_data_start__" "-Wl,--out-implib,bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\boost_serialization-mgw-mt-1_33_1.lib" -mthreads -s -shared -Wl,--allow-multiple-definition -mno-cygwin -o "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\boost_serialization-mgw-mt-1_33_1.dll" -L"" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\basic_archive.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\basic_archive_impl.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\basic_iarchive.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\basic_oarchive.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\basic_iserializer.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\basic_oserializer.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\basic_pointer_iserializer.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\basic_pointer_oserializer.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\basic_serializer_map.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\basic_text_iprimitive.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\basic_text_oprimitive.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\basic_xml_archive.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\binary_iarchive.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\binary_oarchive.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\extended_type_info.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\extended_type_info_no_rtti.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\extended_type_info_typeid.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\polymorphic_iarchive.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\polymorphic_oarchive.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\stl_port.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\text_iarchive.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\text_oarchive.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\void_cast.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\xml_grammar.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\xml_iarchive.obj" "bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\xml_oarchive.obj" ...failed gcc-Link-action bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\boost_serialization-mgw-mt-1_33_1.dll bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\boost_serialization-mgw-mt-1_33_1.lib... ...removing bin\boost\libs\serialization\build\boost_serialization.dll\mingw\release\threading-multi\boost_serialization-mgw-mt-1_33_1.lib ...skipped <@boost!lib>boost_serialization-mgw-mt-1_33_1.dll for lack of <@boost!libs!serialization!build\boost_serialization.dll\mingw\release\threading-multi>boost_serialization-mgw-mt-1_33_1.dll... ...skipped <@boost!lib>boost_serialization-mgw-mt-1_33_1.lib for lack of <@boost!libs!serialization!build\boost_serialization.dll\mingw\release\threading-multi>boost_serialization-mgw-mt-1_33_1.lib... gcc-Link-action bin\boost\libs\signals\build\boost_signals.dll\mingw\debug\boost_signals-mgw-d-1_33_1.dll bin\boost\libs\signals\build\boost_signals.dll\mingw\debug\boost_signals-mgw-d-1_33_1.lib Creating library file: bin\boost\libs\signals\build\boost_signals.dll\mingw\debug\boost_signals-mgw-d-1_33_1.lib bin\boost\libs\signals\build\boost_signals.dll\mingw\debug\slot.obj: In function `ZN5boost7signals6detail9slot_base17create_connectionEv':c:/e2e/win32/ref/boost/boost_1_33_1/libs/signals/build/../src/slot.cpp:47: undefined reference to `boost::signals::trackable::signal_connected(boost::signals::connection, boost::signals::detail::bound_object&) const' collect2: ld returned 1 exit status ...... ...failed gcc-Link-action bin\boost\libs\signals\build\boost_signals.dll\mingw\release\threading-multi\boost_signals-mgw-mt-1_33_1.dll bin\boost\libs\signals\build\boost_signals.dll\mingw\release\threading-multi\boost_signals-mgw-mt-1_33_1.lib... ...removing bin\boost\libs\signals\build\boost_signals.dll\mingw\release\threading-multi\boost_signals-mgw-mt-1_33_1.lib ...skipped <@boost!lib>boost_signals-mgw-mt-1_33_1.dll for lack of <@boost!libs!signals!build\boost_signals.dll\mingw\release\threading-multi>boost_signals-mgw-mt-1_33_1.dll... ...skipped <@boost!lib>boost_signals-mgw-mt-1_33_1.lib for lack of <@boost!libs!signals!build\boost_signals.dll\mingw\release\threading-multi>boost_signals-mgw-mt-1_33_1.lib... FileClone stage\lib\boost_thread-mgw-mt-d-1_33_1.lib HardLink stage\lib\boost_date_time-mgw-mt-d.lib ...skipped <@boost!lib>boost_filesystem-mgw-d.lib for lack of <@boost!lib>boost_filesystem-mgw-d-1_33_1.lib... ...skipped <@boost!lib>boost_filesystem-mgw-mt-d.lib for lack of <@boost!lib>boost_filesystem-mgw-mt-d-1_33_1.lib... ...skipped <@boost!lib>boost_filesystem-mgw.lib for lack of <@boost!lib>boost_filesystem-mgw-1_33_1.lib... ...skipped <@boost!lib>boost_filesystem-mgw-mt.lib for lack of <@boost!lib>boost_filesystem-mgw-mt-1_33_1.lib... HardLink stage\lib\boost_program_options-mgw-d.lib HardLink stage\lib\boost_program_options-mgw-mt-d.lib HardLink stage\lib\boost_python-mgw-d.lib HardLink stage\lib\boost_python-mgw-mt-d.lib HardLink stage\lib\boost_python-mgw.lib HardLink stage\lib\boost_python-mgw-mt.lib HardLink stage\lib\boost_regex-mgw-d.lib HardLink stage\lib\boost_regex-mgw-mt-d.lib HardLink stage\lib\boost_regex-mgw.lib ...skipped <@boost!lib>boost_serialization-mgw-d.lib for lack of <@boost!lib>boost_serialization-mgw-d-1_33_1.lib... ...skipped <@boost!lib>boost_serialization-mgw-mt-d.lib for lack of <@boost!lib>boost_serialization-mgw-mt-d-1_33_1.lib... ...skipped <@boost!lib>boost_serialization-mgw.lib for lack of <@boost!lib>boost_serialization-mgw-1_33_1.lib... ...skipped <@boost!lib>boost_serialization-mgw-mt.lib for lack of <@boost!lib>boost_serialization-mgw-mt-1_33_1.lib... ...skipped <@boost!lib>boost_signals-mgw-d.lib for lack of <@boost!lib>boost_signals-mgw-d-1_33_1.lib... ...skipped <@boost!lib>boost_signals-mgw-mt-d.lib for lack of <@boost!lib>boost_signals-mgw-mt-d-1_33_1.lib... ...skipped <@boost!lib>boost_signals-mgw.lib for lack of <@boost!lib>boost_signals-mgw-1_33_1.lib... ...skipped <@boost!lib>boost_signals-mgw-mt.lib for lack of <@boost!lib>boost_signals-mgw-mt-1_33_1.lib... HardLink stage\lib\boost_thread-mgw-mt-d.lib ...failed updating 24 targets... ...skipped 36 targets... ...updated 22 targets... ------------- end: bjam build output ------------ Thanks, --- Jeffrey

1 0

asio and boost
by bringiton bringiton 17 Jul '06

17 Jul '06

I'm just wondering when the asio networking library will become part of the boost library. I read in the link below that the library has been accepted. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1974.html

2 2

Re: [Boost-users] [iterator] reverse_iterator from iterators thatreturn references to data in self.
by Seb Martel 17 Jul '06

17 Jul '06

"David Abrahams" <dave(a)boost-consulting.com> wrote in message news:<uwtafgdi0.fsf(a)boost-consulting.com>... > "Seb Martel" <smartel(a)real.com> writes: > > > Hello, > > > > given something like: > > > > class ProxyIterator > > : public boost::iterator_facade<ProxyIterator, Costly, boost::random_access_traversal_tag> > > { > > public: > > ProxyIterator(FactoryOfCostly* pF, int i ) : m_pFactory( pF ), m_index( i ) > > {} > > private: > > friend class boost::iterator_core_access; > > void decrement() {--m_index;} > > // ... and others > > > > Costly& dereference() const > > { > > m_value = m_pFactory->MakeCostlyAtIndex( m_index ); > > return m_value; > > } > > private: > > FactoryOfCostly* m_pFactory; > > int m_index; > > mutable Costly m_value; > > }; > > You might need to do something to prevent this from being reported as > a valid random access (or even forward) iterator. 24.1.3: > > --- If a and b are both dereferenceable, then a == b if and only if *a > and *b are the same object. > As in &(*a) == &(*b) ? That's just cruel. But then again, vector<bool> comes to mind... Which reminds me: Is http://boost.org/libs/iterator/doc/new-iter-concepts.html making any progress ? > > You could build a reverse_iterator like the one you propose by storing > the inner iterator within a boost::optional wrapper, and only > initializing it upon dereference. > I might just name it the DamnYou2413ReverseIterator. Tx! -seb

2 1

Macro to contruct/allocate a shared_ptr?
by bringiton bringiton 17 Jul '06

17 Jul '06

I'm trying to define a MACRO that creates a shared_ptr and hides memory allocation. Here is what i have so far: #define NEW0(T) boost::shared_ptr<T>(new T()); #define NEW1(T, p1) boost::shared_ptr<T>(new T(p1)); #define NEW2(T, p1, p2) boost::shared_ptr<T>(new T(p1, p2)); #define NEW3(T, p1, p2, p3) boost::shared_ptr<T>(new T(p1, p2, p3)); --------------------------------- Example of usage for the type Test: class Test { public: Test() {;} Test(int p1) {;} Test(int p1, char p2) {;} Test(int p1, char p2, std::string p3) {;} }; boost::shared_ptr<Test> p0 = NEW0(Test); boost::shared_ptr<Test> p1 = NEW1(Test, 100); boost::shared_ptr<Test> p2 = NEW2(Test, 100, 'a'); boost::shared_ptr<Test> p3 = NEW3(Test, 100, 'a', "hello"); --------------------------------- Is there a better way to do this? I would prefer to use a function instead of a MACRO. But I don't think it is possible because it is not know how many paramaters are in T's constructor. // not sure how to do this (or whether possible) // i am not sure how to implement the variable parameters // (hense the .. in my syntax) template <class T> boost::shared_ptr<T> New(...) { boost::shared_ptr<T> p(new T(...)); return p; } Any ideas? I often have problems with the c++ syntax when creating my own containers because i want to allocate T within the implementation (instead of passing pointers and having the user manage the memory).

6 13

Regex build problem using g++ under cygwin
by Nindi Singh 16 Jul '06

16 Jul '06

Hi Darren .... I had problems with Boost Python which i think which were similar to yours .... i managed to get around them .... take a look at the subject 'Boost Python not linking under Cygwin' posted 16 Jul 14:16 let me know if indeed it is the same problem .. and if the soltuion works for you N

1 0