- Boost - lists.boost.org

[filesystem3] CP_ACP vs CP_THREAD_ACP
by Yechezkel Mett 25 Nov '10

25 Nov '10

Whilst moving from filesystem v2 to v3 on Windows I found that the library uses CP_THREAD_ACP to convert between narrow and wide filenames. This is wrong, as I will attempt to explain. Background: Windows uses a number of locales and language settings as described on the following page: http://msdn.microsoft.com/en-us/library/dd319088(v=VS.85).aspx The relevant ones are Language for non-Unicode programs (System Locale), Standards and Formats (User Locale) and Thread Locale. The System Locale defines which code page is used by the system for narrow chars, and is set by the user system-wide. The User Locale is for formatting numbers and sorting and is set by the user system-wide. The Thread Locale is also for formatting numbers and sorting, is per-thread, and defaults to the User Locale but can be changed by the program; however it is recommended in a number of places not to touch it (although the exact reasons seem vague, apparently it can have surprising effects). CP_ACP gives the System Locale code page. CP_THREAD_ACP gives the Thread Locale code page which is rather a strange item considering that the Thread Locale isn't meant for code pages at all! "ANSI" (ie narrow char) API functions (including CreateFileA) use the System Locale code page (CP_ACP). fopen (VC++9.0) just passes the filename through to the Windows API and therefore also uses CP_ACP. fstream (VC++9.0) uses mbstowcs_s, which uses the global C locale (not the global C++ locale). Narrow char windows use CP_ACP. boost.filesystem should therefore either use CP_ACP (to be consistent with the Windows API, fopen and the GUI) or the global C++ locale (to be consistent with fstream). (Using the global C locale seems a strange idea, but since setting the global C++ locale automatically sets the global C locale as well, that seems a good compromise.) Using CP_ACP gives something that "just works", it's almost certainly what is needed. Using the global C++ locale is perhaps theoretically correct; it can be set (by the user) to match CP_ACP as follows: std::locale::global(std::locale(str(boost::format(".%||") % GetACP()).c_str(), LC_CTYPE)); which is likely the correct thing for most programs anyway, and also allows the user to choose something different should that be necessary. (Unfortunately std::locale("") doesn't do the right thing - it takes the user locale for everything, including code page, and as explained above the user locale has nothing to do with code page.) In many (perhaps most) cases the user locale and system locale will be the same, but not always - for example I have the user locale set to English UK (for dates) but the system locale set to Hebrew (I need to be able to use Hebrew in non-Unicode programs). Yechezkel Mett

1 0

[config] compiler/gcc.hpp version 4.5 to update
by vicente.botet 25 Nov '10

25 Nov '10

Hi, in gcc.hpp the last know version is 4.4 // last known and checked version is 4.4 (Pre-release): #if (__GNUC__ > 4) || ((__GNUC__ == 4) && (__GNUC_MINOR__ > 4)) # if defined(BOOST_ASSERT_CONFIG) # error "Unknown compiler version - please run the configure tests and report the results" Is there any new features that should be updated for gcc-4.5? Even if gcc-4.6 has not been released yet it will be useful to update the file for this version also. In particular I'm interested in the consexpr feature. How can I help? Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

3 11

[context] build error with -std=c++0x
by Charlls Quarra 25 Nov '10

25 Nov '10

Hi, i'm trying to get boost.context (from boost vault) to build with g++ 4.4.1 and 4.5.1 with -std=c++0x on both compilers i'm getting this error: In function `main': test.cpp:(.text+0x94): undefined reference to `boost::contexts::context::operator=(boost::contexts::context&&)' collect2: ld returned 1 exit status the test case is the following code: ------- test.cpp -------------- #include <boost/context.hpp> #include <iostream> using namespace std; void CallWrapper(void* p) { cout << " inside CallWrapper " << endl; }; int main() { boost::context ctx; boost::context current = boost::context::current(); ctx = boost::context::create(CallWrapper, current , 0 , boost::context::default_stacksize); cout << " after creating the context, before executing it " << endl; current.jump_to(ctx); cout << " after executing the context " << endl; }; ----------------------------------- i built the code with this command line: g++ -std=c++0x `pkg-config --cflags boost-1.43` test.cpp -o xtest `pkg-config --libs boost-context` -lboost_context -lboost_system when i remove -std=c++0x from the command line, the code compiles and runs fine Charles J. Quarra

4 4

[move] problem with msvc-10 (BOOST_MOVABLE_BUT_NOT_COPYABLE)
by Oliver Kowalke 25 Nov '10

25 Nov '10

-------- Original-Nachricht -------- Betreff: [move] problem with msvc-10 (BOOST_MOVABLE_BUT_NOT_COPYABLE) Datum: Wed, 24 Nov 2010 20:56:46 +0100 Von: Oliver Kowalke <oliver.kowalke(a)gmx.de> An: boost(a)lists.boost.org Hi, msvc-10 has some problems with boost.move. linker error: LNK2019: unresolved symbol "private __cdecl X::X(class X const&)" Example doc_file_descriptor.cpp (uses BOOST_MOVABLE_BUT_NOT_COPYABLE) does not compile too. g++-4.4.5 accepts the code. ? thx, Oliver #include <boost/move/move.hpp> #include <boost/shared_ptr.hpp> class X { private: BOOST_MOVABLE_BUT_NOT_COPYABLE( X); struct impl_t {}; boost::shared_ptr< impl_t > impl_; X( boost::shared_ptr< impl_t > const& impl); public: X(); static X create(); X( BOOST_RV_REF( X) other); X & operator=( BOOST_RV_REF( X) other); void swap( X & other); }; X::X() : impl_() {} X::X( boost::shared_ptr< impl_t > const& impl) : impl_( impl) {} X X::create() { boost::shared_ptr< impl_t > impl( new impl_t() ); return X( impl); } X::X( BOOST_RV_REF( X) other) : impl_() { impl_.swap( other.impl_); } X & X::operator=( BOOST_RV_REF( X) other) { if ( this != & other) { X tmp( other); swap( tmp); } return * this; } void X::swap( X & other) { impl_.swap( other.impl_); } int main(int argc, char * argv[]) { X x( X::create() ); return 0; }

3 3

[1.45.0] release note are insufficient
by Akira Takahashi 25 Nov '10

25 Nov '10

I have translated the release notes of 1.45.0 into Japanese now(but, don't .qbk). https://sites.google.com/site/boostjp/document/version/1_45_0 In the work, I found the missing library in release note: - Polygon : rev.66403 - Property Tree : #4340 - Serialization : rev.65965, rev.66030, rev.66107, rev.66123 - Thread : #4727, #4531, #2330 -- Akira Takahashi Blog : http://d.hatena.ne.jp/faith_and_brave/

13 14

[config] Variadic template macros in gcc header
by Edward Diener 24 Nov '10

24 Nov '10

Why is there two mutually exclusive macros indicating variadic template support for gcc ? There is the established BOOST_NO_VARIADIC_TEMPLATES which says that any compiler does not have variadic template support. Then I find that for gcc there is also BOOST_HAS_VARIADIC_TMPL which evidently says that the compiler does have variadic template support, and is in no other compiler header file than the gcc one. Since the two config macros are mutually exclusive in the gcc header file, why is there any need for BOOST_HAS_VARIADIC_TMPL ?

4 12

[build] bjam in boost/tools/build/v2/test doesn't work
by Jim Bell 22 Nov '10

22 Nov '10

Running bjam in boost/tools/build/v2/test doesn't (seem to) run build's regressions. Instead, I get: jamfile.jam:8: in modules.load rule project-root unknown in module Jamfile</F:/tmp/boost-MinGW-32/trunk/boost/t ools/build/v2/test>. F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:314: in load-jamfile F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:62: in load F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:168: in project.find F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2\build-system.jam:569: in load F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\..\kernel\modules.jam:283: in import F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\..\kernel\bootstrap.jam:14 2: in boost-build F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\boost-build.jam:14: in module scope If I run "python absolute_sources.py" (to pick that test as an example), I get very little (and it doesn't match regression test output): F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\TestCmd.py:60: Deprecation Warning: The popen2 module is deprecated. Use the subprocess module. import popen2 Am I close? I realize that build is a different animal. Are there instructions for running its tests in isolation? (Could those instructions be put in boost/tools/build/v2/index.html?) If you're reading this on the boost-build list, please CC me as I'm not subscribed. Thanks, -Jim PS: My apologies if I missed a response to this. I posted it last week on boost.

3 3

[accumulators] serialization support
by Zoran Angelov 22 Nov '10

22 Nov '10

Hi, Have anyone considered for boost.accumulators having a serialization support? It will be helpful for example in situations where data is being accumulated/sampled on long time intervals, and persistence of boost.accumulators objects is impossible. Something like this: boost/accumulators/statistics/count.hpp: . . . template<typename Sample, typename Tag> struct immediate_mean_impl : accumulator_base { // for boost::result_of typedef typename numeric::functional::average<Sample, std::size_t>::result_type result_type; template<typename Args> immediate_mean_impl(Args const &args) : mean(numeric::average(args[sample | Sample()], numeric::one<std::size_t>::value)) { } template<typename Args> void operator ()(Args const &args) { std::size_t cnt = count(args); this->mean = numeric::average( (this->mean * (cnt - 1)) + args[parameter::keyword<Tag>::get()] , cnt ); } result_type result(dont_care) const { return this->mean; } template <typename Archive> void serialize(Archive &ar, const unsigned int version) { ar & BOOST_SERIALIZATION_NVP(mean); } private: result_type mean; }; . . . The problem is that members, storing the state are private. Thanks

2 2

[1.45][signals2] Can't build PDF docs?
by John Maddock 21 Nov '10

21 Nov '10

I'm trying to build the signals2 docs for the PDF doc distribution, but I'm failing with: warning: failed to load external entity "hello_world_def_code_snippet.xml" tutorial.xml:50: element include: XInclude error : could not load hello_world_def_code_snippet.xml, and no fallback was found warning: failed to load external entity "hello_world_single_code_snippet.xml" tutorial.xml:52: element include: XInclude error : could not load hello_world_single_code_snippet.xml, and no fallback was found warning: failed to load external entity "hello_def_code_snippet.xml" tutorial.xml:63: element include: XInclude error : could not load hello_def_code_snippet.xml, and no fallback was found etc... I can see that process_snippets.exe is being invoked, but I can't find the output xml files anywhere. This occurs if I either build from within the doc/pdf directory, or the libs/signals2/doc directory. Any ideas? Thanks, John.

3 6

[1.45] Beta version of PDF docs available.
by John Maddock 21 Nov '10

21 Nov '10

There's a beta build of the PDF docs for 1.45 here: http://sourceforge.net/projects/boost/files/boost-docs/1.45.0/boost_1_45_pd… If library authors could check for the usual snafu's, and I'll build the final versions in a few days. Regards, John.

3 2