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

Re: Re: Unresolved symbols in regex libs on tru64
by Mark Helzer 10 Dec '04

10 Dec '04

>> Sam results with static linking. >> I'm not good with reading mangled names but it looks to me like they >> are there. Am I perhaps missing a link option? > >I'm not familiar with the True64 linker so I can't say. What happens if you build the >examples with bjam - do those all build OK? > >John. OK I think I found it -- using the ansi object model $cxx -c ... -model ansi I have always just accepted the default - arm. It was in the man page for cxx and also in the documentation for the tru64cxx65 toolset. I should read more carefully. So it looks like all the code has to use ansi or arm, since I have a LOT of stuff compiled in the arm mode, it would be better to build boost using the "-sBUILD=<object-model>arm" switch, however now I'm back to compile errors: cxx: Error: /adp/local/src/boost_1_32_0/libs/program_options/build/../src/convert.cp p, line 62: #434 a reference of type "wchar_t *&" (not const-qualified) cannot be initialized with a value of type "wchar_t [32]" detected during instantiation of "std::basic_string<charT, std::char_traits<charT>, std::allocator<charT>> ...

3 2

Re: [Boost-users] simple regex compile error
by Brian Gaber 10 Dec '04

10 Dec '04

On AIX would it make a difference if I used the gcc compiler? If so, what would you recommend for the compiler command? Thanks. Brian

2 1

Newbie using multi_index
by Hammann, Jochen 10 Dec '04

10 Dec '04

Hello, I'm new in using the MultiIndex container of Boost 1.32.0. To get familiar with this library I wrote a small example. During the compilation with the Microsoft Visual C++ 7.1 compiler I encounter an internal compiler error. The error occurs, if I use the MultiIndex container with the following configuration: - Specification of tagged indices. - Specification of one composite_key template parameter. - Specification of at least three indices. Example: struct SFirst { }; struct SSecond { }; struct SBoth { }; typedef std::pair<std::wstring, std::wstring> Element_t; typedef multi_index_container<Element_t, indexed_by<ordered_non_unique<tag<SFirst>, member<Element_t, std::wstring, &Element_t::first> >, ordered_non_unique<tag<SSecond>, member<Element_t, std::wstring, &Element_t::second> >, ordered_unique<tag<SBoth>, composite_key<Element_t, member<Element_t, std::wstring, &Element_t::first>, member<Element_t, std::wstring, &Element_t::second> > > > > MultiIndex_t; //... int main(int argc, char** argv) { MultiIndex_t test; MultiIndex_t::index<SBoth>::type& both = test.get<SBoth>(); return 0; } If I compile this code I get the following internal compiler error: d:\Libraries\DLLs\Boost\Boost_1_32_0\inc\boost\tuple\detail\tuple_basic.hpp(612) : fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'msc1.cpp', line 2701) Please choose the Technical Support command on the Visual C++ Help menu, or open the Technical Support help file for more information If I try to access the first (#0) and second (#1) index with their respective tags, everything works fine. Also, I'm able to access all three indices by their numerical value without an error. Is the declaration of the MultiIndex_t typedef wrong? Regards, Jochen.

4 5

[iostreams] Version of Iostreams compatible with 1.32 available
by Jonathan Turkanis 10 Dec '04

10 Dec '04

Hi All, A version of the Iostreams library designed to work with release 1.32 is now available: http://home.comcast.net/~jturkanis/iostreams/ This version does not incorporate all the changes decided on during the review, but most of the name changes have been applied. In particular, - The library is now contained entirely in the iostreams subdirectories of <boost> and <libs>. - Resources are now called Devices - The i/o mode Inout has been renamed Bidirectional - The concept Buffered has been renamed Multi-Character - Filters are now located in the directory boost/iostreams/filter - Devices are now located in the directory boost/iostreams/device The library has been tested on VC7.1, Intel 7.1-8.0 for Windows, Codewarrior 8.3 and GCC 3.2 (mingw). Unfortunately, I have noticed some regressions of GCC 3.3-4, but am working to correct them. I am confident that the library will eventually work on GCC 3.3+ and Borland 5.6.4. In addition, I may be able to provide limited support for VC6-7.0. I'm hoping to get a version into CVS soon. Also, several of the fixes that people sent me during the review have been removed because they caused regressions. They have not been forgotten -- they will be incorporated in to the final version in modified form. -- Jonathan Turkanis technews(a)kangaroologic.com

1 0

shared/weak_ptr conventions?
by Niklas Wiberg 10 Dec '04

10 Dec '04

Hi, I have a question that I believe is more a matter of taste than one of functional correctness... Say that I have a model (see Basket below) that formally owns the heap-objects (see Apple below). Basket has a function that is merely a query (hasApple) and involves no ownership-changes. Also assume that there is good reason that Apple:s are allocated on the heap... On one hand, I can see how using a weak_ptr as the parameter type would signal to users that hasApple has no intention of modifying ownership of the pointed-to object. On the other hand, in order to actually use the pointee (search for it in this case), hasApple must convert the weak_ptr to shared_ptr (lock() or shared_ptr constructor), so it would seem more pragmatic to just use shared_ptr as the parameter type. class Apple; class Basket { std::vector< boost::shared_ptr<Apple> > m_contents; bool hasApple( shared OR weak_ptr<Apple> a); // no transfer ...more functions }; Is there a "good style" concensus on how to choose smart pointer type for function arguments among boost smart pointer users? Best regards, Niklas Wiberg

2 1

[variant] BOOST_VARIANT_LIMIT_TYPES and BOOST_MPL_LIMIT_LIST_SIZE
by Christopher D. Russell 09 Dec '04

09 Dec '04

I'm trying to increase the number of bounded types stored in a boost::variant. It seems like I should be able to #define BOOST_MPL_LIMIT_LIST_SIZE in multiples of ten prior to inclusion of any boost headers but this doesn't seem to work for me. I haven't upgraded to the latest 1_32_0 release yet and am working with out-of-the-box 1_31_0 on Windows using the MS 7.1 compiler (VS .NET 2003). If for example I define BOOST_MPL_LIMIT_LIST_SIZE as: #define BOOST_MPL_LIMIT_LIST_SIZE 20 #include "my_boost_headers.h" I get an error: d:\ENCAPSULE-EXTLIB\boost\boost_1_31_0\boost_1_31_0\boost\variant\detail\make_variant_list.hpp(54) : error C2977: 'boost::mpl::list' : too many template arguments d:\ENCAPSULE-EXTLIB\boost\boost_1_31_0\boost_1_31_0\boost\mpl\aux_\preprocessed\plain\list.hpp(124) : see declaration of 'boost::mpl::list' d:\ENCAPSULE-EXTLIB\boost\boost_1_31_0\boost_1_31_0\boost\variant\detail\make_variant_list.hpp(59) : see reference to class template instantiation 'boost::detail::variant::make_variant_list<T0,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19>' being compiled Shouldn't this just work? What am I missing here. TIA - Chris

1 0

Boost.Serialization link errors (VC++ 7.0)
by Ray Hilton 09 Dec '04

09 Dec '04

I get 17 link errors trying to compile a very simple example from the touturial section of the documention (what im trying to compile is listed at the end of this post verbatim). My enviorment is all default except for an include path to boost. Any solution? #include <fstream> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> class gps_position { private: friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & degrees; ar & minutes; ar & seconds; } int degrees; int minutes; float seconds; public: gps_position(){}; gps_position(int d, int m, float s) : degrees(d), minutes(m), seconds(s) {} }; int main() { std::ofstream ofs("filename"); boost::archive::text_oarchive oa(ofs); const gps_position g(35, 59, 24.567f); oa << g; ofs.close(); std::ifstream ifs("filename", std::ios::binary); boost::archive::text_iarchive ia(ifs); gps_position newg; ia >> newg; ifs.close(); return 0; }

3 6

Compile error of data_time
by zhengyi 09 Dec '04

09 Dec '04

boost-users: Here is a new user's letter for help: when i compile the whole boost(version_1_32_0), it show some error of data_time. the file greg_month.cpp failed. in the lexical_cast.hpp，line 126 string_type s(boost::lexical_cast<string_type>("not-a-date-time")); the compiler said : binary '>>' : no operator found which takes a right-hand operand of type_put<Config,charT,OutputIterator>::string_type' (or there is no acceptable conversion) When tracing down the error message, I found that [[date_names_put::string_type]] actually means [[std::basic_string<charT>]] and in file lexical_cast.hpp line 146 -- 168 there are right overload of operator>>. Why the compiler complain about can't find the wellformed operator? My Compiler is msvc71 and STLport-5.0-0125 was installed with it's own iostream. the cmdline is bjam "-sVC71_ROOT=D:\Program Files\Microsoft\Microsoft Visual Studio .NET 2003\Vc7" "-sSTLPORT_PATH=D:\Program Files\Programming_Tools\STLport-5.0-0125\stlport" "-sSTLPORT_5.0-0125_PATH=D:\Program Files\Programming_Tools\STLport-5.0-0125" "-sSTLPORT_VERSIONS=5.0-0125" "-sTOOLS=vc-7_1-stlport" "--prefix=D:\Program Files\Programming_Tools\Boost_1_32" install --with-date_time this problem has killed so many brain cells of mine ! 　　　　　　　　　　　　　　zhengyi 　　　　　　　　　　　　　　goodmen(a)x263.net 　　　　　　　　　　　　　　　　　2004-12-08

3 2

Re: [Boost-users] simple regex compile error
by Brian Gaber 09 Dec '04

09 Dec '04

I tried moving <boost/regex.hpp> to be the first include statement, but got the same error. I tried the following compile statement: /usr/vacpp/bin/xlc++ -c -DNDEBUG -O3 -qstrict -qinline -qnotempinc -qfuncsect -qeh -qrtti regex.cpp -o regex -I /usr/local/include and again got the same error as before. Any other suggestions? What is the ETA of the fix you mentioned.

2 1

Re: Unresolved symbols in regex libs on tru64 (John Maddock)
by Mark Helzer 09 Dec '04

09 Dec '04

2 1