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

Re: [Boost-users] [bcp] [shared_ptr] [wave] Extracting subsetofboostforshared_ptr - 3.2MB?
by Nat Goodspeed 19 Feb '06

19 Feb '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of David Abrahams > Sent: Saturday, February 18, 2006 1:42 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] [bcp] [shared_ptr] [wave] Extracting > subsetofboostforshared_ptr - 3.2MB? > > > Wouldn't it > > work just to point bcp to the compiler of interest -- by giving it the > > name of one of a set of small prepackaged files that #defines the > > vendor-specific compiler-predefined macros that Boost cares about -- > > Also, there are macros introduced by Jamfiles and configuration macros > set by users in their own Jam/Make/whateverfiles. Unless you know > what their values will be ahead of time, you may leave out some files > the user will need. [Nat] Okay. But the reason I suggested capturing a compiler's typical #defines in a config file was to enable a user to create a custom one containing their own #defines as well. Heh, the custom config file wouldn't need to *clone* the generic one packaged with bcp: it could #include the generic one and then add to it.

1 0

Regex++
by Winson Yung 19 Feb '06

19 Feb '06

Hello all, I am a new user of Boost Regex++, I have seen some strange behavior from the return of Regex++. Not sure this is the right mailing list to ask such a question or not. If not, please refer me to the right one. Here is my question: My program is written in MFC, and it has been built under both Visual C++ 6 and Visual Studio .NET 2003. Under Visual Studio .NET 2003, the following code returns result = 1, however expr[1].c_str() always returns an empty string. boost::RegEx expr(itField->GetFieldRegEx(), TRUE); unsigned int result = expr.Grep(v, wholeFileStr); if (result != 0) { for (int i = 1;i <= itField->GetMatchNum();i++) { const char *buf = expr[i].c_str(); // Get match result if (std::strlen(buf) == 0) { The same code works fine under Visual C++ 6 with the same content inside wholeFindStr.

2 2

[pkg-boost-devel] Boost on Debian
by Steve M. Robbins 19 Feb '06

19 Feb '06

Hello Dave, I'm responding to your message on boost mailing list http://lists.boost.org/Archives/boost/2006/02/100262.php Domenico Andreoli also contributed to this response. Apologies for the tardy response. I read the list very infrequently via web archives and I have only just noticed the message. So you ask: I am going to be trying to write some new "getting started" documentation for Boost for the upcoming release. I would really like to include some information about what people can expect when they get Boost packages from their Debian, RedHat, whatever distribution. All of our documentation so far is written from the perspective that users have a complete Boost CVS tree, but I guess that's not true for everyone? Can you fill us in? The short answer is: someone wishing to develop code using Boost under Debian need install the package libboost-dev (and, possibly, other -dev packages like libboost-filesystem-dev). The headers as well as static and shared library files are all installed into standard linux locations. Compilation and linking is done with no special options other than specifying the library; e.g. "-lboost_filesystem". Our goal is to make the Debian Boost library packages as much like standard libraries as possible. For Debian, this means that headers and link-time library files are contained in a "-dev" package. In addition, for each library that builds a shared object, we have a separate, versioned package, e.g. "libboost-filesystem1.33.1". Normally, however, one isn't concerned with the library package because the "-dev" package depends on the shared library package and installing the former automatically brings in the latter. The list of all -dev packages can be obtained by looking at what libboost-dev suggests with standard Debian tools like "aptitude" or "apt-cache". The "-dev" package contains the "release" build with both single- and multi-threaded versions, in both static and shared flavours for a total of 4 libraries. So the developer may choose to link using "-llibboost_filesystem-gcc-1_33_1" or " "-llibboost_filesystem-gcc-mt-1_33_1", shared or static. We also provide a shorthand symbolic link for the multithreaded version; you can use just "-llibboost_filesystem" (shared or static). In addition to the "-dev" packages, we have libboost-doc (documentation) bcp boost-jam boost-build (v2) Finally, there is a "libboost-dbg" package that contains the debug build of all the shared libraries, both single- and multi-threaded. Hope this is helpful, -Steve _______________________________________________ pkg-boost-devel mailing list pkg-boost-devel(a)lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-boost-devel

1 0

[Boost.Build v2] doc defect
by jth01＠arcor.de 18 Feb '06

18 Feb '06

Hello, /doc/src/advanced.xml introduces the unit-test rule but says nothing about import testing ; being necessary in order to use it. I'm not sure: Are trivial reports like this desired? Jens

1 0

[Tuple documentation] Maybe a bug
by raulh39＠ya.com 18 Feb '06

18 Feb '06

Hello Newsgroup, I think that in "libs/tuple/doc/tuple_advanced_interface.html" there is a mistake: "The template access_traits defines three type functions. Let T be a type of an element in a tuple: 1. access_traits<T>::type maps T to the return type ... " There is no such member "::type". ¿Maybe it is "::non_const_type"? Best regards, Raúl.

1 0

(no subject)
by raulh39＠ya.com 18 Feb '06

18 Feb '06

Hello Newsgroup, I think that in "libs/tuple/doc/tuple_advanced_interface.html" there is a mistake: "The template access_traits defines three type functions. Let T be a type of an element in a tuple: 1. access_traits<T>::type maps T to the return type ... " There is no such member "::type". ¿Maybe it is "::non_const_type"? Best regards, Raúl.

1 0

Many error when building Boost libraries
by Rob Marsden 18 Feb '06

18 Feb '06

I see many compilation problems here in the list, so I hope you will forgive me adding to the clutter. Can someone tell me what I'm doing wrong or missing to get the following. When building Boost 1.33.0, the date_time, program_options and wave libraries fail to build. I am after the program_options in particular. My environment is intel_win32 running in the MSVC v6 IDE. The output from the build runs to 176Kb, but of the very many errors, the typical ones are: C:\Libraries\boost_1_33_0\libs\program_options\build\../src/options_description.cpp(378): error: too few arguments for class template "std::reverse_iterator" find(reverse_iterator<string::const_iterator>(line_end - 1), C:\Libraries\boost_1_33_0\libs\program_options\build\../src/variables_map.cpp(81): error: no instance of overloaded function "std::set<_K, _Pr, _A>::insert [with _K=std::string, _Pr=std::less<std::string>, _A=std::allocator<std::string>]" matches the argument list argument types are: (std::set<std::string, std::less<std::string>, std::allocator<std::string>>::iterator, std::set<std::string, std::less<std::string>, std::allocator<std::string>>::iterator) object type is: std::set<std::string, std::less<std::string>, std::allocator<std::string>> xm.m_final.insert(new_final.begin(), new_final.end()); ^ These recur many times in the program_option builds, plus things like: C:\Libraries\boost_1_33_0/boost/lexical_cast.hpp(156): error: no operator ">>" matches these operands operand types are: std::basic_stringstream<char, std::char_traits<char>, std::allocator<char>> >> boost::date_time::date_names_put<boost::gregorian::greg_facet_config, wchar_t, std::ostreambuf_iterator<wchar_t, std::char_traits<wchar_t>>>::string_type stream >> output && ^ detected during: instantiation of "bool={bool} boost::detail::lexical_stream<Target, Source>::operator>>(InputStreamable &) [with Target=boost::date_time::date_names_put<boost::gregorian::greg_facet_config, wchar_t={unsigned short}, std::ostreambuf_iterator<wchar_t={unsigned short}, std::char_traits<wchar_t={unsigned short}>>>::string_type, Source=boost::detail::array_to_pointer_decay<const wchar_t={unsigned short} *>::type={const wchar_t={unsigned short} *}, ... and so on to ... instantiation of "boost::date_time::all_date_names_put<Config, charT, OutputIterator>::all_date_names_put(const charT *const *, const charT *const *, const charT *const *, const charT *const *, const charT *const *, charT, boost::date_time::ymd_order_spec, boost::date_time::month_format_spec) [with Config=boost::gregorian::greg_facet_config, charT=wchar_t={unsigned short}, OutputIterator=std::ostreambuf_iterator<wchar_t={unsigned short}, std::char_traits<wchar_t={unsigned short}>>]" -- Rob Marsden Gistix (Northern) Limited

3 4

How to store the result of boost::bind?
by David Williams 18 Feb '06

18 Feb '06

Hi, if I call boost::bind it creates a function object, is that correct? So how can I give this function object a name? That is, presumably I can have an expression like: SomeTypeHere myFunc = boost::bind(...); But what should SomeTypeHere actually be? I've found I can use boost::function but would rather not for performance reasons. Any other options? Thanks, David

3 3

Un-nesting a class
by Perry Smith 18 Feb '06

18 Feb '06

I have a template like: template <typename Z> class foo { // ... I know that Z has the form A::B::C (three levels of nesting). Does boost have a way for me to define a type which refers to A::B? Thanks, Perry

2 1

Re: [Boost-users] Un-nesting a class
by Sohail Somani 17 Feb '06

17 Feb '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Perry Smith > Sent: Friday, February 17, 2006 11:24 AM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] Un-nesting a class > > I have a template like: > > template <typename Z> > class foo { // ... > > I know that Z has the form A::B::C (three levels of nesting). Does > boost have a way for me to define a type which refers to A::B? typedef ab A::B; ?

2 1