- Boost - lists.preview.boost.org

Fw: Re your copyright in Boost C++ Library
by John Maddock 17 Aug '04

17 Aug '04

And yet another permission.... ----- Original Message ----- From: "Lars Gullik Bjønnes" <larsbj(a)lyx.org> To: "John Maddock" <john(a)johnmaddock.co.uk> Sent: Tuesday, August 17, 2004 1:57 PM Subject: Re: Re your copyright in Boost C++ Library > "John Maddock" <john(a)johnmaddock.co.uk> writes: > > >> | Hi, if you are receiving this message it is because there are one or > | more > >> | files in the Boost C++ libraries that contain your copyright > | declaration. > >> > >> I belive that my name (and copyright) should just be removed from > >> those files. > > > | Are you sure? > > If it is ok by you, yes. > (if not just add me to the blanket file. Or do that anyway...) > > > > | You can view the two files here: > > > | http://cvs.sourceforge.net/viewcvs.py/boost/boost/boost/detail/atomic_count… > | http://cvs.sourceforge.net/viewcvs.py/boost/boost/boost/detail/lwm_gcc.hpp?… > > > | cvs revision history suggests that the implementation originally came from > | you? > > It is really something of an super simple adaptation of code that was > already in boost. And I belive that this has be rewritten a bit since > even. (and it is even buggy... or so they say :-) ) > > -- > Lgb >

1 0

Fw: Re your copyright in Boost C++ Library
by John Maddock 17 Aug '04

17 Aug '04

Another permission for out records... ----- Original Message ----- From: "Nikolay Mladenov" <nickm(a)sitius.com> To: <boost-owner(a)lists.boost.org> Sent: Tuesday, August 17, 2004 3:03 PM Subject: Re: Re your copyright in Boost C++ Library > I Nikolay Mladenov, give > permission for all my contributions to Boost to be moved to the Boost > Software License Version 1 >

1 0

ETI bug and iterators
by Yitzhak Sapir 17 Aug '04

17 Aug '04

Hello. I am in the process of upgrading code to use boost 1.31.0 for MSVC6.5. During this process I happened upon minimum_category.hpp which contains "ETI workarounds". Now, it seems that the ETI workarounds cause the compilation to fail, with the error message: constant expression expected. Particularly, we are creating zip iterators to two STLPort vectors. In debug iterator mode, I get the following error. (minimum_category.hpp was modified a bit, but the problem is in the instantiation of boost::is_same<T1 or T2,int>). If I remove the ETI "workarounds" the code compiles fine. So my question is what is ETI, what does the ETI workaround provide, and how can I benefit from both the workaround and normal use of the code? The code looks something like: std::find(boost::make_zip_iterator(boost::make_tuple(vector1.begin(), vector2.begin())), boost::make_zip_iterator(boost::make_tuple(vector1.end(), vector2.end())), ... The beginning of the error looks something like this: ./../3rdParty\boost/iterator/detail/minimum_category.hpp(86) : error C2057: expected constant expression ../../3rdParty\boost/iterator/detail/minimum_category.hpp(112) : see reference to class template instantiation 'boost::detail::minimum_category<struct boost::random_access_traversal_tag,struct boost::random_access_traversal_tag>' being compi led ../../3rdParty\boost/mpl/aux_/preprocessed/msvc60/apply.hpp(88) : see reference to class template instantiation 'boost::detail::minimum_category<struct boost::mpl::arg<1>,struct boost::mpl::arg<2> >::apply<struct boost::random_access_travers al_tag,struct boost::random_access_traversal_tag>' being compiled ../../3rdParty\boost/mpl/aux_/preprocessed/msvc60/apply.hpp(101) : see reference to class template instantiation 'boost::mpl::aux::msvc_apply2<struct boost::detail::minimum_category<struct boost::mpl::arg<1>,struct boost::mpl::arg<2> > >::re sult_<struct boost::random_access_traversal_tag,struct boost::random_access_traversal_tag>' being compiled ../../3rdParty\boost/iterator/zip_iterator.hpp(173) : see reference to class template instantiation 'boost::mpl::apply2<struct boost::detail::minimum_category<struct boost::mpl::arg<1>,struct boost::mpl::arg<2> >,struct boost::random_access_ traversal_tag,struct boost::random_access_traversal_tag>' being compiled Thanks.

2 1

CVS at boost-consulting.com
by Christoph Ludwig 17 Aug '04

17 Aug '04

Hi, my Boost CVS working directory used to be rooted at :pserver:anonymous@boost-consulting.com:/boost. However, for some time I didn't get any updates any more. Since it's not plausible that there were no check-ins in the last week I checked out the boost directory from SourceForge. And indeed, there are many differences between the two working directories. For instance: After `cvs up' I have revision 1.4 of boost/algorithm/string/classification.hpp in the working directory rooted at boost-consulting and its status is up-to-date according to `cvs stat' (no sticky tag or date). But in the working directory rooted at sourceforge there's revision 1.5. `cvs log' says it was checked in on 2004-07-30. Even if the CVS at boost-consulting is mirrored only once a day, revision 1.5 of boost/algorithm/string/classification.hpp should be in the repository by now. Do others experience the same problem? Regards Christoph -- http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/cludwig.html LiDIA: http://www.informatik.tu-darmstadt.de/TI/LiDIA/Welcome.html

2 1

[Boost-bugs] [ boost-Bugs-1010681 ] boost::filesystem::exists is broken on cygwin
by SourceForge.net 17 Aug '04

17 Aug '04

Bugs item #1010681, was opened at 2004-08-17 14:19 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1010681&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Carlo Wood (libcw) Assigned to: Nobody/Anonymous (nobody) Summary: boost::filesystem::exists is broken on cygwin Initial Comment: Compile the following code snippet: #include <iostream> #include <boost/filesystem/path.hpp> #include <boost/filesystem/operations.hpp> int main() { boost::filesystem::path p = "/usr"; if (!boost::filesystem::exists(p)) std::cerr << p.string() << " doesn't exist according to boost::filesystem" << std::endl; } $ uname -a CYGWIN_NT-5.0 vmware 1.5.10(0.116/4/2) 2004-05-25 22:07 i686 unknown unknown Cygwin $ g++ -g -I"/usr/src/install/3.3.1/include/boost-1_31" test.cc -L"/usr/src/install/3.3.1/lib" -lboost_filesystem-gcc-d-1_31 $ ./a.exe /usr doesn't exist according to boost::filesystem Needless to say that /usr does exist: $ ls -ld /usr drwxrwxrwx+ 18 carlo Gebruike 4096 Aug 8 14:49 /usr ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1010681&group_… ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: tru64 ICE
by David Abrahams 17 Aug '04

17 Aug '04

Daveed Vandevoorde <daveed(a)edg.com> writes: > Hello, > > On Aug 16, 2004, at 2:57 PM, David Abrahams wrote: > [...] >> This construct is causing tru64cxx6.5 to ICE. Is there any chance >> this is an old bug of yours for which you know a workaround, or is it >> all Compaq? > > We couldn't get it to abort in our released versions > of the last few years. So our suspicion is that this > is a Compaq-specific issue. > > Is there anything in the wording of the internal error > message (if any) that would indicate that it originates > in an EDG front end? Nobody showed me the actual error, so I can say. Sorry :( Thanks for looking at this. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com

2 1

[boost.test] basic_cstring troubles with tru64cxx65
by Markus Schöpflin 17 Aug '04

17 Aug '04

I think I have found the source of the internal compiler errors currently preventing boost.test to work with the toolset tru64cxx65. The following small sample fails to compile and gives me an internal compiler error when compiled with cxx. ---%<--- #include <boost/test/detail/basic_cstring/basic_cstring.hpp> using namespace boost::unit_test; // void foo(const_string const & s) // ok void foo(const_string s) // not ok { } int main() { foo(literal_string("foo")); return 0; } --->%--- Changing the declaration of foo() makes the compiler error go away. I'm currently thinking that the compiler perhaps has problems with the automatically generated copy constructors for the class basic_cstring. I tried writing an explicit copy constructor for basic_cstring but this doesn't seem to help. The compiler still crashes. Maybe someone else working with this platform has any ideas... Markus

2 3

Re: [boost] Re: 31 character limit for filenames
by Steve Ramsey 17 Aug '04

17 Aug '04

On Mon, 16 Aug, 2004, at 11:34 pm, Miro Jurisic wrote: > Steve Ramsey <steve(a)lucena.com> wrote: >> FSRefs can only refer to pre-existing file system objects - this >> merited a >> single sentence in a single tech note far away from the File Manager >> documentation - which makes them bloody useless for general path >> conversions. > > You probably want CFURL APIs for path conversions. However, you should > explain a > little more what you mean by path conversions, as there are some > non-trivial and > very subtle issues regarding HFS paths and Unicode characters. (But > they may be > completely irrelevant to you, which is why I ask what you mean.) I'm not sure sure how helpful the CFURL stuff is for what I'm doing, as I'm not sure there's an easy way to get HFS paths out of them when running under OS X (as I hinted before, why on earth would you want an HFS path at all under OS X, except to make the MSL happy). The path conversion was an obscure reference to one of my failed cunning plans to convert POSIX paths to HFS paths by having FSPathMakeRef/FSRefMakePath do the work for me; I was toggling the gestaltFSUsesPOSIXPathsForConversion bit in the gestaltFSAttr Gestalt selector between calls. This fails in the general case since FSRefs can't refer to non-existent objects, but it neatly side-steps the text encoding issues when the object does exist. In the absence of system-level hacks, I'm hoping this sort of path conversion isn't the answer. I'm now looking into re-writing certain low-level MSL source files such as path2fss.c to use POSIX paths instead of HFS paths, as there is precedent for Boost libraries providing alternative MSL files to overcome certain deficiencies (boost::thread, for example). Really, though, at this point I'm just fishing while I wait for an elegant solution to suggest itself, where elegant is something other than writing off the MSL for Mac development. Here's a quick summary of what I'm dealing with: the goal is to be able to use boost::filesystem with Metrowerks CodeWarrior and the Metrowerks StdLib/STL implementation, MSL, on a CFM Carbon program intended to run under OS 9 and OS X. Ideally, only a source implementation should be necessary, and the interface files and MSL source should be off-limits (although I'm thinking some interface files needs to be changed to be more generic, e.g. handle-body idiom for path, or I need to throw this restriction out and just litter the interface files with more preprocessor conditionals and give the classes target-specific privates). The POSIX path will not work in this scenario since the MSL uses HFS paths (HFS paths: multi-root, colon delimiters, specify relative paths in the reverse fashion of POSIX, often Pascal strings in Carbon API calls, C strings in MSL calls). You can get a lot of mileage out of a proper rewrite of fs::path::native_file_string, but for total compliance work also needs to be done in fs::operations. Without system-level conversions to handle all the gritty details, the key solution here will probably be to write a heroically specialized manual HFS<->POSIX path converter that takes into account things like multiple roots (e.g., faking a /Volumes directory under OS 9), File Manager name mangling, and possible weird issues with aliases and symbolic links (mmm...cross-volume aliases). I'd _really_ like to avoid going this route... Steve

2 1

Re: [boost] 31 character limit for filenames
by Steve Ramsey 17 Aug '04

17 Aug '04

On Mon, 16 Aug, 2004, 9:03 am, Doug Gregor wrote: > Okay, it's time to ask again: do we still need to enforce the > 31-character limit on filenames? AFAIK, we have this for MacOS 9, only. > Is that platform still significant for Boost users? I believe that the native file name size for ISO 9660 Level 2 is also 31 (32) characters, which affects a whole lot of CDs. What library does this relate to? There might be an easy way to provide an extension, depending on intended use. Speaking of Macs and filenames, has anyone created a successful implementation of boost::filesystem for use with the Metrowerks MSL? I've been trying to shoehorn one into the filesystem interfaces for a week, now, and I'm alternately cursing Metrowerks and Apple. This might be the final indignity that finally drives me away from CFM and the MSL and into the prickly, awkward arms of Mach-O and the BSD stdlib. Two highlights of my wobbly path: 1) MSL only supports HFS paths, even for POSIX-alike functions; 2) FSRefs can only refer to pre-existing file system objects - this merited a single sentence in a single tech note far away from the File Manager documentation - which makes them bloody useless for general path conversions. Right now, I'm thinking my best bet is to go with a tainted implementation that leverages off of Apple's old MoreFiles sample code. This wouldn't necessarily be compatible with the BSL, however, which makes contributing something useful to the library dicey. All this for cross-platform fstreams... Steve

2 1

generalized arithmetic functors
by Neal D. Becker 17 Aug '04

17 Aug '04

STL defines some common arithmetic operators, such as template<typename T> struct plus { T operator+(const T&, constT&); }; There is a need for more general operators: template<typename T1, typename T2, typename res> struct plus { res operator+(const T1&, constT2&); }; For example, std::complex<double> + double -> std::complex<double>. Has there been any discussion on this issue?

2 3