- Boost - lists.boost.org

[serialization] MS VS 2005 warning
by Adam Badura 22 Jan '08

22 Jan '08

When I use boost::serialization on MS VS 2005 I have some warnings even on level 3. The warnings are: 1) warning C4267: 'argument' : conversion from 'size_t' to 'std::streamsize', possible loss of data j:\thirdparty\boost_1_34_1\boost\archive\basic_binary_oprimitive.hpp 136 2) warning C4267: 'initializing' : conversion from 'size_t' to 'std::streamsize', possible loss of data j:\thirdparty\boost_1_34_1\boost\archive\basic_binary_iprimitive.hpp 144 3) warning C4267: '=' : conversion from 'size_t' to 'std::streamsize', possible loss of data j:\thirdparty\boost_1_34_1\boost\archive\basic_binary_iprimitive.hpp 154 4) warning C4267: 'initializing' : conversion from 'size_t' to 'unsigned int', possible loss of data j:\thirdparty\boost_1_34_1\boost\serialization\collections_save_imp.hpp 38 [And this seems to me an obvious error, the variable "count" should be declared as "Container::size_type".] 5) warning C4996: 'std::basic_streambuf<_Elem,_Traits>::sgetn': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' j:\thirdparty\boost_1_34_1\boost\archive\basic_binary_iprimitive.hpp 148 [This seems to be MS specific problem which should be solved on project level.] 6 ) warning C4996: 'std::basic_streambuf<_Elem,_Traits>::sgetn': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' j:\thirdparty\boost_1_34_1\boost\archive\basic_binary_iprimitive.hpp 159 [This seems to be MS specific problem which should be solved on project level.] Can anything be done (especially in case of warning 1-4)? Adam Badura

1 0

Re: [boost] [circular_buffer] some comments and suggestions
by Jan Gaspar 22 Jan '08

22 Jan '08

#1 yes, I agree the default capacity will be zero then. And I like the idea of assertion in push_back, insert... I can change it in the trunk but I'm not sure I should chage it in the 1.35 release branch at this stage. #2 Coud you show the example how do you want to get the special iterator? #3 yes, it makes sense Jan ----- Original Message ---- From: Thorsten Ottosen <thorsten.ottosen(a)dezide.com> To: boost(a)lists.boost.org Sent: Monday, 21 January, 2008 9:54:46 PM Subject: Re: [boost] [circular_buffer] some comments and suggestions Jan Gaspar skrev: > #1 > I don't agree. I tried to design the circular_buffer as close as possible to the other std containers. > Suppose the cirular_buffer does not allocate anything on construction - this means when you insert an element to the buffer, it will not be inserted because the capacity is 0. > I think this is unnatural for std containers. On the other hand there is a note in the documentation that you should >avoid using this constructor: "This constructor has been defined only due to compatibility with the STL container definition. Avoid using it because it may allocate very large amount of memory." My point is that you cannot always control the use of the default constructor ... libraries call it now and then, and it pretty much renders circular_buffer unusable with those libraries. Insertion is already different for circular_buffer, so I don't think it is that important that push_back() does not insert anything. Instead, add an assertion check to all insertion function that the capacity is > 0, and specify this as a precondition to all those functions. > #2 > Agree with is_linearized(), I don't agree with special iterator - I cannot see the point - just use pointers as you mentioned. Right, but I would prefer an easy, idiomatic way to get those pointers. > #3 > Yes, maybe in the next version. What would be the method signature? I guess this would be handy: void rotate( const_iterator newBegin ); precondition: newBegin in [begin(),end()). if we added a new overload taking three iterator arguments like, std::rotate(), I think it might not yield any performance improvement over the std::version. -Thorsten _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost __________________________________________________________ Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com

2 1

Re: [boost] [circular_buffer] some comments and suggestions
by Jan Gaspar 21 Jan '08

21 Jan '08

#1 I don't agree. I tried to design the circular_buffer as close as possible to the other std containers. Suppose the cirular_buffer does not allocate anything on construction - this means when you insert an element to the buffer, it will not be inserted because the capacity is 0. I think this is unnatural for std containers. On the other hand there is a note in the documentation that you should avoid using this constructor: "This constructor has been defined only due to compatibility with the STL container definition. Avoid using it because it may allocate very large amount of memory." #2 Agree with is_linearized(), I don't agree with special iterator - I cannot see the point - just use pointers as you mentioned. #3 Yes, maybe in the next version. What would be the method signature? Regards, Jan ----- Original Message ---- From: Thorsten Ottosen <thorsten.ottosen(a)dezide.com> To: "boost(a)lists.boost.org" <boost(a)lists.boost.org> Sent: Monday, 21 January, 2008 11:40:23 AM Subject: [boost] [circular_buffer] some comments and suggestions Hi Jan, #1 I was browsing through the docs in trunk. First I noticed that the default constructor has the follwoing postcondition: capacity() == max_size() && size() == 0 I find that somewhat unfortunate that it allocates a huge amount of memory. It seems to me that it is too easy to do that by coincidence. The usual rule for std containers is to never allocate by default and anticipate a call to reserve() or the first element. It also seems to me that this will create problems when the container is used in containers that might use default construction. #2 I think it would be useful to add a predicate called is_linearized(), so one can check if this property holds. Also, if this do hold, I should be able the get fast iterators to this linear segment, perhaps by calling .base() on the iterators which then simply return a pointer (I know I can get the pointers by array_one(), but I would more often need the iterators). #3 I think it would be useful to add rotate() as a member function. AFAICT, it can in many times (if not all) be much faster than std::rotate() because it can simply move a few elements and then simply adjust the iterators. -Thorsten _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost __________________________________________________________ Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com

2 1

Critical bugfix for Boost.Function on 12/19
by Chad Walters 21 Jan '08

21 Jan '08

I just noticed this announcement on the Boost home page: December 19, 2007 - Critical Bug in Function Library * Boost.Function in Boost 1.34.x has a bug that affects the construction of Boost.Function objects in a multi-threaded context. The problem has been fixed in the Boost trunk and for the upcoming Boost 1.35.x. To patch your Boost 1.34.x, copy the files function_base.hpp and function_template.hpp into the Boost directory boost/function. Two questions come to mind, one technical and the other procedural: 1. What other Boost libraries make use of Boost.Function in a way that might tickle this particular bug? I'd like to understand if we are being affected by this in any way and while we aren't using Boost.Function directly, perhaps we are using it indirectly. More generally, is there a good way to understand which Boost libraries are dependent on which other libraries? 2. I can't seem to find any mention of this on the user, devel, or announce mailing lists. Is there some place besides the home page where things like this get publicized? I guess I would have expected this to come through on at least of one of those three lists. Thanks for any insights. Chad

3 3

Boost.Python without Python
by Edson Tadeu 21 Jan '08

21 Jan '08

Hi, Boost.Python has a great dispatch mechanism, complete with type and methods registry, and works nice with template types (given the instantiations), and overloading -- with the extra bonus of working across shared-object boundaries. It could be very useful for many other purposes, if it were not so tied to Python. I'm thinking about multi-methods / multiple dispatching / generic factories / plug-ins. Shared objects that register extensions when loaded, e.g., register new concrete objects and new specializations for already existent methods. Is there any library that already does this? Can the non-python code be easily separated from the python-dependent code in Boost.Python? Is there already some effort to do something like this? Thanks in advance, Edson

2 1

Review Request: Egg
by shunsuke 21 Jan '08

21 Jan '08

(Sorry, this is repost: subject format might be wrong.) I request my Boost.Egg library be enqueued into the formal review queue. The online document: http://p-stade.sourceforge.net/boost/libs/egg/ The brief description is found at: http://lists.boost.org/Archives/boost/2008/01/132301.php Regards, -- Shunsuke Sogame

1 0

Trac open bugs - by assignee
by Marshall Clow 21 Jan '08

21 Jan '08

[ 208 open tickets today, 195 last Monday ] [ I go away for a week, and this happens! ;-) ] If you are maintaining a library, and have not logged into the trac system at <http://svn.boost.org/trac/boost/>, please do so ASAP. Until you do that, no tickets can be assigned to you, and will remain under "None". Instructions on working with tickets can be found at: <http://svn.boost.org/trac/boost/wiki/TicketWorkflow> and a mapping of user names to "real names" can be found at: <http://svn.boost.org/trac/boost/report/16> Bug summary 19 az_sw_dude 17 dgregor 15 djowel 14 grafik 14 None 12 doug_gregor 12 agurtovoy 11 dave 8 vladimir_prus 8 jsiek 7 anthonyw 6 rogeeff 6 johnmaddock 6 bemandawes 5 witt 5 turkanis 3 pdimov 3 nesotto 3 jmaurer 3 igaztanaga 3 ebf 3 danielw 2 urzuga 2 pavol_droba 2 nasonov 2 matias 2 danieljames 2 <Blank> 1 t_schwinger 1 speedsnail 1 shammah 1 samuel_krempp 1 ramey 1 marshall 1 kaalus 1 hljin 1 hkaiser 1 garcia 1 dlwalker 1 burbelgruff 1 aaron_windsor <Blank> 1307 [lambda] invalid boostbook <Blank> 1434 Boost.Preprocessor_ small fix for the documentation None 1068 Mersenne twister disables streaming for Visual C++ None 1094 Finding the correct library to link (feature request for pkg-config support)h None 1222 lambda::ret<T> should declare result_type. None 1247 Typos in "boost/random/additive_combine.hpp"_ lines 68-69 None 1270 uniform_smallint doesn't compile with lagged_fibonacci random number generators None 1407 Boost is doesn't install on MacPorts using Leopard None 1493 SVN files making it through to install None 1515 [lambda] C4512 warnings from VC8.0 None 1544 uniform_01 w/ref template param causes ref to ref error None 1546 Method boost::random::uniform_int::operator()(engine_ value) is missing None 1548 [variant][docs]typo: formal arg_ operand_ should be v in times_two arglist None 1570 Some boost headers aren't ready for gcc 4.3 None 1572 [lambda] smart pointer const-ness affects its contents None 1573 Broken URL in copyright boiler-plate aaron_windsor 778 top-level configure is broken agurtovoy 1001 gcc 4.1.2 segfaults on mpl/test/apply.cpp agurtovoy 1051 MPL header ordering triggers bug agurtovoy 1099 unable to iterate through a "non-explicitly-declared" mpl::set agurtovoy 1215 Boost 1.34.1_ mpl: Wrong workaround detection using MinGW32 (or.hpp_ line #33) agurtovoy 1317 has_xxx randomly broken in msvc agurtovoy 1469 [mpl] nested typedef of set has two different meanings agurtovoy 1476 always<> is not nullary. agurtovoy 1528 g++ 4.3.0 reports error because of redeclaration of next agurtovoy 1549 Boost.MPL: 'index_of' algorithm is not documented agurtovoy 1568 duplicate include guards agurtovoy 588 mpl::remove compile error with gcc 4.1.0 agurtovoy 640 documentation mistake anthonyw 1154 tss destruction segfaults in conjunction with dlopen/dlclose anthonyw 1168 [thread] tss crashes randomly anthonyw 1268 xtime_cmp changes to deal with overflow were reverted anthonyw 1470 Boost.Thread: Compilation errors with non-__cdecl calling convention anthonyw 1547 [thread] error C2065: 'NULL' : undeclared identifier in thread_primitives.hpp anthonyw 876 xtime documentation incomplete anthonyw 881 errors when build with Apache stdcxx az_sw_dude 1028 typo in boost header: date_time/time_defs.hpp az_sw_dude 1078 from_iso_string cannot read the output from to_iso_string az_sw_dude 1098 Urgent libboost-date-time1.33.1 : bugs on ia64 ? az_sw_dude 1147 date_time library contains global #define ERROR az_sw_dude 1160 warning: month_format shadows a member of this az_sw_dude 1162 warning: ticks shadows a member of this az_sw_dude 1289 posix_time::time_facet forgets to pass a_ref argument to base class az_sw_dude 1299 change in typedef stringstream_type in format_date_parser.hpp causing compilation error az_sw_dude 1306 invalid docbook in date_period.xml az_sw_dude 1384 Linking problem with date_time library on Visual C++ 2008 Express az_sw_dude 1386 date_time documentation Jamfile breaks building of boost docs az_sw_dude 1524 format_date_parser.hpp(221) : cannot convert parameter 1 az_sw_dude 1574 operator<< for boost::posix_time::ptime ignores ostream flags az_sw_dude 287 wrong usage of ios_base::narrow az_sw_dude 316 date_time type conversion warning az_sw_dude 604 from_ftime incorrectly processes FILETIME filled with zeros az_sw_dude 642 operator<< for gregorian::date_duration not found az_sw_dude 889 Insane Dependencies az_sw_dude 890 date_time library supports only the current dst rule bemandawes 1378 filesystem path invalid name for hidden files (LINUX) bemandawes 1389 filesystem::ostream << boost::format generates operator ambigious error (in MSVC++) bemandawes 1458 Darwin Tiger throws std::runtime_error: locale::facet::_S_create_c_locale name not valid bemandawes 1578 bug in readdir_r_simulator() in a multi-threaded environment bemandawes 1583 Serious flaw in boost::filesystem filename handling (opensuse) bemandawes 752 directory_iterator doesn't work with catch burbelgruff 1503 typeof bug (big integral constant) danieljames 1554 When BOOST_HASH_NO_EXTENSIONS is defined hash doesn't support new string types. danieljames 1555 When BOOST_HASH_NO_EXTENSIONS is defined hash doesn't support boost::system::error_code danielw 1044 Argument pack inaccessable in a functions return type danielw 1054 Parameter takes an "infinite" amount of time to compile with the Intel compiler. danielw 1097 keyword.hpp generates many warnings C4180: qualifier applied to function type has no meaning; ignored dave 1010 linking boost.python on freebsd dave 1019 iterator_facade::pointer should be the return type of operator-> (DR 445) dave 1085 Python rules for compiling in Mac OS X dave 1179 [boost.python] can not export a union in VC2005sp1 dave 1181 [boost.python] can modify enum value dave 1387 Review / update docs to reflect changes dave 1460 Python classes with multiple bases are convertible only to the first class in the lists dave 1482 boost::python::throw_error_already_set should be marked noreturn dave 1516 [python] Failing VC9 regression tests dave 865 Use of C++0x keyword as identifier dave 910 gcc strict-aliasing problems with python dgregor 1003 [iostreams] copy-paste error in typedefs for wchar multichar_filters dgregor 1139 [iostreams] Regex filter segfaults when zero matches found dgregor 1140 boost::iostreams linked_streambuf bug dgregor 1149 Minor doc error in basic_null_device dgregor 1164 Floyd Warshall broken with unsigned edge weights dgregor 1185 iostreams::direct_streambuf<T_Tr>::is_open always returns false if output iterator is not null dgregor 1192 [boostbook] problem when two files have the same name dgregor 1199 configure doesn't work with path containing whitespaces (MacOS X) dgregor 1232 mapped_file_source::is_open() is broken under windows dgregor 1310 [result_of] const-qualified function pointer doesn't work dgregor 1326 Unable to check graph isomorphism using LEDA adapter dgregor 1391 dominator_tree_test on Borland/CodeGear outputs overly long line dgregor 1394 Translate libs/graph/build/python/Jamfile to BBv2 dgregor 1395 Write Tests for Python Bindings dgregor 556 Bundled graph properties dgregor 732 Johnson All-Pairs needs better "no path" information dgregor 736 Const correctness violation djowel 1170 Emit Warnings instead of # symbols in the syntax highlighter djowel 1171 Quickbook title output djowel 1172 non-utf djowel 1176 Space after inline code djowel 1206 Escaping from within code? djowel 1273 CR+LF newlines in position_iterator djowel 1276 spirit problem with _GLIBCXX_DEBUG djowel 1277 Closing section like [pre with } causes Quickbok to crash djowel 1280 sections in imported source files get put inside <para> elements in docbook output djowel 1281 Quickbook produces invalid BoostBook/DocBook XML djowel 1324 tuple should have a swap() that operates element-by-element djowel 1396 wrong result_of invocation around transform_view djowel 1436 [quickbook] inline code inside headings djowel 1484 Quickbook produces illegal docbook for some docinfo fields. djowel 1500 [Spirit/Phoenix] C4512 Compiler warnings from VC8 dlwalker 613 boost/crc.hpp uses non-standard conforming syntax doug_gregor 1021 [Graph][reverse_graph] Problem using reverse_graph adapter with an adapted user defined graph doug_gregor 1076 compile error: disconnecting struct with operator()() doesn't work in VS2005 SP1 doug_gregor 375 LEDA graph adaptors do not handle hidden nodes properly doug_gregor 402 random_vertex/random_edge are unnecessarily inefficient doug_gregor 403 Document copy_component doug_gregor 447 reverse_graph and constness of property maps doug_gregor 708 Dijkstra no_init version should not require VertexListGraph doug_gregor 733 Numbered headers don't work with "preferred" syntax doug_gregor 735 Fruchterman-Reingold grid performance can be improved doug_gregor 738 Memory leaks with signal::connect? doug_gregor 829 Implicit graph not implement doug_gregor 852 Problem with Boost and GCC 4.1 ebf 1507 [variant] C4512 warnings from VC8.0 ebf 965 [doc] boost::variant tutorial - final example uses v1_v2 should be seq1_seq2 ebf 993 Variant should use least common multiple of alignments_ rather than maximum garcia 1581 Boost.MultiArray: Resizing bug if the index is not 0-based grafik 1041 Cygwin requires PATH setting. grafik 1062 Cygwin install stage fails with combination of patches grafik 1322 trac rejects patch attachment as spam grafik 1417 Regresson tests hang in Darwin (Tiger) grafik 1430 Regression fails under Cygwin grafik 1433 Trac's spam detection rejects too many valid messages grafik 1512 Broken link to vacpp in bjam docs. grafik 1513 Broken link to bcpp in bjam docs. grafik 1571 boost bugtracker displays a patch incorrectly grafik 1576 cannot read non-ASCII output messages grafik 1577 Some commands don't work because hStdInput == 0 grafik 616 Boost Jam_ and non english directorys grafik 959 linking fails when Boost is compiled with STLport 5.1.* on Linux (names mismatch) grafik 986 Problem building Python modules on boost 1.34.0 hkaiser 1079 boost-1.34.0 fails to compile. concept checks not satisfied. hljin 1522 bit_range friend decl in bit_aligned_pixel_reference.hpp needs to be fully qualified for gcc 4.3 mainline igaztanaga 1080 boost::interprocess win32 global file mapping issue igaztanaga 1210 interprocess::barrier hangs during second use under linux (boost 1.33.1) igaztanaga 1390 Interpocess: managed shared memory failing completely under OS X jmaurer 351 Diff in state of mersenne_twister gen between GCC3.41 & CW9 jmaurer 599 uniform_01 copies engine instead of using a reference jmaurer 819 uniform_int<> with type's maximum availaible range error johnmaddock 1081 Empty string rejected as perl-style regex johnmaddock 1314 Using SSE-intrinsics in VC8 causes static assert in type_with_alignment.hpp johnmaddock 1411 Fix BOOST_PARTIAL_SPECIALIZATION_EXPLICT_ARGS johnmaddock 1446 POSIX API doesn't use C locale johnmaddock 1451 error: use of C99 long long integer constant johnmaddock 1582 BOOST_HAS_LONG_LONG is defined when it shouldn't be jsiek 1531 segfault in dynamic_bitset::reference assign operator jsiek 1540 Poisson distribution very slow for large mean (and may also overflow). jsiek 416 Spelling of Edmonds-Karp-Algorithm jsiek 575 Calling subgraph::global_to_local on a root graph jsiek 636 strange compiling problem for transitive_closure jsiek 815 remove_edge core dumps on self-circle jsiek 875 No iterator based constructor for adjacency_matrix jsiek 900 graphml reader namespace handling is broken kaalus 1184 property_tree assignment (operator) bug marshall 1252 [pool] severe overhead with unaligned sizes. matias 1406 Understanding the Tables outdated matias 1539 Missing semi-colon in random library quitck start example nasonov 1220 lexical_cast requires RTTI nasonov 754 boost::any - typeid comparison across shared boundaries nesotto 1284 [range] sub_range assignment issue nesotto 1464 boost_range_array unused in several array_size() functions nesotto 1565 iterator_range disables msvc warning 4996 pavol_droba 1152 rle_example fails pavol_droba 1385 begin must be boost-qualified pdimov 1106 shared_ptr<T> should not convert to shared_ptr<U> when T* doesn't convert to U* pdimov 1444 scoped_ptr::operator== should be equivalent to a.get()==b.get()_ but is currently !!a==!!b pdimov 779 gcc-4.2 atomicity.h location ramey 1569 serialization doen't build on mingw rogeeff 1383 signal.h features not found on Mac OS rogeeff 1489 BOOST_CHECK_CLOSE fails to compile with templated value type rogeeff 1542 [test] compiler errors when building with stdcxx library rogeeff 1560 Performance testing with boost::test rogeeff 1561 Using BOOST_AUTO_TEST_CASE with boost::program_options rogeeff 1566 Missing example files in documentatio samuel_krempp 859 boost::format ignores a user defined locale shammah 386 boost::pool_allocator breaks with vector of vectors speedsnail 1138 Problems with TSS and static thread library t_schwinger 1100 Building boost.function_types fails cvs rev-1.1_ no chdir command in bash turkanis 1523 [iostreams] VC8/VC9 compiler warnings turkanis 1545 [boost/rational.hpp] 'noskipws' is not a member of 'std' turkanis 1575 boost_bzip2 contains the symbol "main" turkanis 1579 gzip compressor should model DualUseFilter turkanis 1580 Add static assert to prohibit instantiating a chain with mode dual_use urzuga 574 [boost::lambda] Compile error with libstdc++ debug mode urzuga 781 Lambda: (_1 + "y")(string("x")) Doesn't Compile vladimir_prus 1165 more quoting problems vladimir_prus 1274 Useless error message vladimir_prus 1321 invalid docbook in tool documentation vladimir_prus 1527 [program_options] Second (and subsequent) lines in tabbed text not aligned correctly vladimir_prus 1530 Program options documentation - Overview - Syntactic Information example typo vladimir_prus 1537 no value given in 'mysql_password =' vladimir_prus 469 multitoken broken vladimir_prus 689 [program_options] Endless loop with long default arguments witt 1046 Boost.Python quickstart instructions mention nonexistent target witt 583 Fixes for build on IBM pSeries for AIX and Linux witt 834 Homepage regression links witt 957 The "Getting Started" page does not mention the stdlib option witt 973 zip_iterator has value_type == reference -- -- Marshall Marshall Clow Qualcomm, Inc. <mailto:mclow@qualcomm.com> The famous British scientist, Lord Kelvin, said: "When you measure what you are speaking about and express it in numbers, you know something about it, but when you cannot (or do not) measure it, when you cannot (or do not) express it in numbers, then your knowledge is of a meagre and unsatisfactory kind."

1 0

64-bit Boost.Integer
by Phil Endecott 20 Jan '08

20 Jan '08

Dear All, Back in April 2007 I posted a patch to add 64-bit ints to Boost.Integer: http://lists.boost.org/Archives/boost/2007/04/119895.php Scott McMurray replied to say that a patch for this was already waiting and hopefully "will get applied once 1.34 is dealt with". As far as I can see, the Boost.Integer in the release branch still doesn't have this: http://svn.boost.org/svn/boost/branches/release/boost/integer.hpp What needs to be done so that this functionality is included in 1.36? Phil.

4 4

accumulators + std::complex
by Neal Becker 20 Jan '08

20 Jan '08

typedef std::complex<double> complex_t; accumulator_set<complex_t,stats<tag::mean,tag::moment<2> > > results in what may be the longest error messages ever. Should this work?

2 2

[filesystem] POSIX compliant readdir_r to fix ticket #1578
by Beman Dawes 20 Jan '08

20 Jan '08

Sun supplies both POSIX and non-POSIX versions of readdir_r, according to http://docs.sun.com/app/docs/doc/819-2243/readdir-3c?a=view. The compliant version is selected by defining _POSIX_PTHREAD_SEMANTICS. So it looks to me that the fix for ticket #1578 (which is reporting the bug that results when the non-POSIX version is used) is to define _POSIX_PTHREAD_SEMANTICS at the beginning of boost-root/libs/filesystem/src/operations.cpp. This will cause the POSIX version to be used. I don't have access to a Sun system so can't test that. There is also a small chance that the same macro is used on some other platform in a conflicting way. I'd appreciate it if someone with access to a Sun system could test this (using the program given in the #1578). If I don't hear anything in a day or so, I'll go ahead and make the change to the trunk. Thanks, --Beman

1 0