August 2004 - Boost - lists.preview.boost.org

numeric/ublas aix test failures
by Michael Stevens 23 Aug '04

23 Aug '04

Hallo Danial, > I am interested in using ublas for a large government project. > I noticed ublas (as of 8-19-2004) failed test3 on the visual age c++ compiler. > What does this test exercise? Test3 exercise the whole spectrum of sparse vector and matrix types with a variety of BLAS operations. These tests are by far the most demanding on the compiler. Unless > We have currently installed the 1.31 libraries. Is this the same code that > produced the test results? The the code the regression test use is take from the HEAD of Boost CVS. This code has been developed a great deal since Boost-1.31 The aim at the moment is to get maximum compiler compatibility. Bar an incorrect commit over the weekend and the recent noncopyable problems this is progressing well. I have cross posted this to the ublas-dev mailing list. This is the best place for uBLAS specific discussion as there are many active contributers. In particular you will find many people who also use Visual age C++ on large systems. Michael -- ___________________________________ Michael Stevens Systems Engineering Navigation Systems, Estimation and Bayesian Filtering http://bayesclasses.sf.net ___________________________________

1 0

Segfault at program exit using memory pools
by Thomas 22 Aug '04

22 Aug '04

Hi all, I'm running into a problem where I'm getting a segfault when my program exits when I use boost's memory pools. If I call purge_memory right before the end of the program, that also produces the segfault. Basically all I'm doing with the pools is calling ordered_malloc to allocate memory for arrays, and then free(myPointer,size_of_array) to de-allocate the memory. Oddly enough, when I run the code through valgrind, I don't get the segfault at all. I'm pretty sure that it's not bad memory or anything like that because none of the other programs I compile & run yields this kind of result. Any thoughts on what might be going wrong? Thanks Tom -- Thomas <hazard(a)imsa.edu>

1 0

Successfully compiled & static linked with Boost.Threads using Visual Studio .NET 2003
by David Barrett 22 Aug '04

22 Aug '04

Hi, I see a lot of people have been having problems statically-linking Boost.Threads with Visual Studio .NET 2003. For what it's worth, I just got it to work, and here's what I did: 1) Created and entered a C:\Libraries folder C:\> Mkdir c:\Libraries C:\> cd c:\Libraries 2) Checked out the latest code from CVS using: (From http://boost.org/more/getting_started.html) cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost login [Hit <return> when it asks for a password] cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost checkout boost cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost logout 3) Installed Boost.Build and Boost.Jam 4) Built everything: C:\Libraries\Boost> bjam --prefix=c:\Libraries\Boost install 5) Launched Visual Studio .NET 2003 6) Created a new Win32 Console Project (CTRL+SHIFT+N) and accompanying solution named BoostTest 7) Configured the wizard to create an Empty Project (click "Application Settings", check "Empty Project", click "Finish") 8) Configured the project to use the "Multi-threaded Debug Runtime Library" (Project::BootTest Properties, C/C++::Code Generation::Runtime Library) 9) Configured the project to search for the Boost include files (Project::BootTest Properties, C/C++::General::Additional Include Directories) by adding: C:\Libraries\boost\include 10) Created a new file named BoostTest.cpp (CTRL+SHIFT+A, click "C++ File", type "BoostTest.cpp" in the Name field, click Open) 11) Inserted the single include line: #include <boost/thread/thread.hpp> 12) Compiled (CTRL+F7) 13) It works! So yes, that all seems pretty obvious. But it took me a long time to get working. I was unable to get anything with a Boost.Thread header to compile *at all* (with any combination of static/dynamic runtimes, #defines, and code hacks) using the 1.31.0 release currently available for download via SourceForge. But it works now, and I'm proof that it can be done. Good luck! -david

1 0

Re: [boost] New design proposal for boost::filesystem
by Reece Dunn 22 Aug '04

22 Aug '04

Carlo Wood wrote: >On Sat, Aug 21, 2004 at 11:36:31AM +0100, John Maddock wrote: > > > I propose the following design. The aim of boost::filesystem should >be to > > > support the following coding idiom: > > > > > > * The programmer should take care to only handle two types of paths > > > in his application: > > > > > > 1) Complete paths > > > 2) Relative paths > > > > That is true now. > >No, the current implementation/design doesn't restrict anything at all >in this regard. You can just use fs::path to store paths - and that is >it. A path is not aware of a distinct difference between complete >paths and relative paths (except that they are complete or relative >of course) - definitely not in the same way as a design would that >uses two different classes for the two. A complete path is one that is fully qualified, thus: fs::path absolute = fs::path( "d:/devel/libraries/boost/1.31.0/libs" ); whereas a relative path is one that is "relative" to another. With a relative path, you must have an absolute path as the basis, e.g.: fs::path relative = fs::path( "../boost/mpl" ); and can turn the relative path into an absolute one by doing: fs::path qualified = absolute / relative; so where is the problem? >The most problematic difference is that it is possible to even store >a third possibility (one that is neither complete nor relative). ??? Do you mean one that isn't relative because it is not based from an absoute path, or that the path does not exist? If so, you can do that in any file system, e.g.: fs::path foobar = fs::path( "../booster/foobar.foo" ); fs::exists( absolute / foobar ); A path will either (in absolute form) refer to a file, a directory or be invalid. > > > * The programmer will have to specifically tell the libary when a > > constructed > > > path is 'native' and when not. A native path is accepted according >to > > native > > > rules and never gives any problem (exceptions) further on. > > > A non-native path is checked according to the existing rules, which > > basically > > > means that the programmer can set a default check routine that will >in > > effect > > > determine how portable the application will be. > > > > That is also true now, isn't it? > >No, because the 'native' that you can specify with the current design >is only a check on the characters used in the directory components, and >only related to the representation of a path - not *marking* the path >as different. The 'native' I am talking about is enforced for complete >paths and reflexs also the root part of a directory ("C:\", "c:/cywgin/", >"/" etc). The essential difference is that a path that is once marked >as 'native' must stay native. It can never be converted to a portable >path anymore. Only relative paths that are portable from the start >can stay portable after certain operations (like appending a directory, or >cutting off a directory at the end). The native you are referring to is an "absolute" path, correct? Boost.Filesystem stores the paths in a generic form. Thus, if your filesystem uses ':' as a directory separator, the library will map this correctly from it's internal state. If you enforce that all "native" Windows paths must have a directory, you are restricting the use of the library, e.g. "\\mycomp\devel\libraries" is not possible! Likewise, it would not be possible to store URLs. NOTE: I am not sure if Boost.Filesystem currently supports URLs, but it should be possible to extend it to add that support. Also, URLs are not attached to a particular filesystem and are thus portable. It should be possible to handle both URLs and native paths, but limiting "native" paths will only make this harder. > > > I propose two design changes: > > > > > > 1) 'native' is now not only a representation, but an *internal state* >of > > fs::path. > > > (this has no effect on the representation as returned by > > fs::path::string()). This would make things too restrictive. I think you are confusing "native" with "absolute" paths, but how do you validate an absolute path? Is there a Windows and a POSIX function to validate an absolute path (e.g. IsPathAbsoute)? It would then be possible to have a fs::is_absolute( ... ) function. > > > 2) All 'complete' paths are automatically marked as 'native'. Likewise, how do you validate a complete path? What about a URL? If you have the URL "http://www.boost.org/people" and are using a system whereby the native directory separator is ':', the URL will be mapped to "http:::www.boost.org:people", corrupting the URL. > > If I understand you correctly, you are suggesting that error checking is > > turned off for native paths, I would support that, but other than that I > > don't see how it differs. > >Heh - the current design does NOT have an internal state that marks >a path as native or not. Hence, it cannot do sensible error checks >that need that knowledge. Isn't that difference enough? Native - as Boost.FileSystem uses it - is used to mark a path as using the native OS syntax for specifying paths. This is so you can do: fs::system_complete( fs::path( argv[1], fs::native ) ); and use the library on Windows, *nix, OpenVMS, MacOS, etc. without having to worry about the differences between how they specify their paths and thus what regular expressions need to be used on the string. The example from the documentation (using OpenVMS) is: DISK$SCRATCH:[GEORGE.PROJECT1.DAT]BIG_DATA_FILE.NTP;5 > > > Examples, the following code is legal: > > > > > > fs::path p1("C:\\foo\\a.exe", native); // As one might do on windows. > > > fs::path p2("/usr/src/a.out, native); // As one might do on linux. > > > std::cout << p1.native_file_string(); // ok, p1 is native. > > > > > > fs::path p3("foo/bar"); // Relative path, always succeeds. > > > std::cout << p.string(); // ok > > > std::cout << p.native_directory_string(); // Useless, but ok. > > > > Not useless at all. And works now. > ^^^^^^^^^^^^^^^^ > \__ this. > >That is not backupped. Did you mean p to be the relative path p3? If so, then p3.native_directory_string() is perfectly valid and *not* useless. If the OS uses ':' as it's directory separator, then this will return "foo:bar". It is useful for all sorts of purposes, like debuging. > > > fs::path p4(complete(p3)); // p4 is now "native", because now it is > > complete. Why does native ==> complete? You can have a native relative and/or complete path. > > > std::cout << p4.string() // Not allowed because p4 is native >(complete). Huh? IIUC path.string() returns the internal format of the path (e.g. "foo/bar") whereas path.native_directory_string() returns the path as represented by the native OS (e.g. "foo:bar"). >Right now you can call all the operations that actually pass a path to some >system call - and UNLESS that path is complete - it will not be >non-portable. Not true. "foo/bar" is relative *and* non-portable for OS's that use ':' as a directory separator. >THAT means that boost::filesystem has a structural design error. You are >now saying that I can complete all paths just prior to calling any >operation >that passes paths to system calls. Would you mind even listing those for >me? >Why not change boost::filesystem so that it takes care of completion >automatically when needed? That way you cannot make errors. If you have an absolute path boost_dir and a relative path boost_build2, you can do: ::SetWorkingDirectory(( boost_dir / boost_build2 ).native_directory_string().c_str()); >As an example - I developed my application first on GNU/Linux with as only >demand that it had to be portable to cygwin. Therefore, I used UNIX paths. >Testing if /usr/src/edragon/edragon/build/src/gui/gui.la existed on linux >worked fine. It did NOT work on cygwin. Because I was stupid? No, I >think >that was because boost::filesystem is not activily supporting portable >programming. Did you check that you have the file where you said on the cygwin system. Have you checked that "/usr/bin/ls.exe" exists? Also, have you checked that BOOST_POSIX is defined as per the note on using the cygwin platform in the docs? Regards, Reece _________________________________________________________________ Express yourself with cool new emoticons http://www.msn.co.uk/specials/myemo

2 1

Review Wizard Status Report
by tom brinkman 22 Aug '04

22 Aug '04

Review Wizard Status Report 1) Summary 2) Review Managers Needed 3) Review Schedule 1) Summary The next three libraries under review extend the c++ iostreams framework through stream modifiers. Please be prepared to discuss these libraries in the coming weeks. 2) Review Managers Needed If you would like to volunteer to be a review manager, please contact me at reportbase(a)yahoo.com. 3) Review Schedule August 21, 2004 More IO August 28, 2004 Iostreams September 7, 2004 Output Formatters September 15, 2004 Mini-Review wiki algorithims September 17, 2004 Smart Containers September 27, 2004 Named Params October 6, 2004 Policy Pointer October 16, 2004 Wave October 26, 2004 Finite State Machine (FSM) November 4, 2004 Fixed Strings August 21, 2004 More IO Author - Daryle Walker - darylew(a)hotmail.com Review Manager - Tom Brinkman - reportbase(a)yahoo.com Download: http://groups.yahoo.com/group/boost/files/more_io_4.zip [or] http://boost-sandbox.sourceforge.net/more_io_4.zip Description: Provides a multitude of I/O-oriented extensions. Some are extra manipulators; variants of "std::endl", a resetting manipulator, and a configurable manipulator. The library includes a set of base class templates for wrapping a new stream-buffer type around a stream class. Changes from the last interim version (called "more_io_3b.zip"): * split the manipulator header into several headers * refined the license statements in some already-affected files Changes from the first formal review (called "more_io.zip"): * refined the interface and implementation of array-streams and stream-buffer wrappers (including a wrapping example) * added the null-stream, value-stream, and pointer-stream headers * added generalizations to the new-line and skip-line manipulators * added the non-oriented 'reset' and 'form' manipulators * split the manipulator header into several headers * changed the license statements August 28, 2004 Iostreams Author - Jonathan Turkanis - turkanis(a)kangaroologic.com Review Manager - Volunteer needed Web-Page: http://home.comcast.net/~jturkanis/iostreams Download: http://home.comcast.net/~jturkanis/iostreams Description: The Iostreams Library serves two main purposes: To allow the easy creation of standard C++ stream and stream buffer classes for new data sources and sinks. To provide a convenient interface for defining i/o filters and attaching them to standard streams and stream buffers. The library focuses on freeing users from writing boiler plate code and allowing them instead to create highly reusable components. In addition to providing an abstract framework the library provides a number of concrete filters, sources and sinks which serve as example applications of the library but are also useful in their own right. These include components for accessing memory-mapped files (based on work of Craig Henderson) , for file access via operating system file descriptors, for code conversion, for text filtering with regular expressions, for line-ending conversion and for compression and decompression in the zlib, gzip and bzip2 formats. September 7, 2004 Output Formatters Author - Reece Dunn - msclrhd(a)hotmail.com Review Manager - John Torjo - john(a)torjo.com Download: http://cvs.sourceforge.net/viewcvs.py/ boost-sandbox/boost-sandbox/boost/outfmt/ [or] http://cvs.sourceforge.net/viewcvs.py/ boost-sandbox/boost-sandbox/libs/outfmt/ Description: The I/O formatters library provides an easy and customizable way to input/output arrays, STL arrays, STL collections, sub-arrays from/to STL streams. It allows you to configure how each element in such an array will be written to the stream or read from the stream, while providing reasonable defaults. September 15, 2004 Mini-Review wiki algorithims Author - Various Review Manager - Tom Brinkman - reportbase(a)yahoo.com Download: to be determined Description: not available September 17, 2004 Smart Containers Author - Thorsten Ottosen - nesotto(a)cs.auc.dk Review Manager - Pavol Droba - droba(a)topmail.dk Download: the boost sandbox: ptr_container Description: The Smart Container Library consists of several container classes that are capable of storing heap-allocated objects in an exception-safe manner. The interface of the container classes effectively hides the underlying pointers so one can work on objects directly; this indirection is done to make the classes safer and easier to use. The library can also be customized to allow, for example, that a container does not rake ownership of the stored objects. September 27, 2004 Named Params Co-Authors - David Abrahams - dave(a)boost-consulting.com) & Daniel Wallin (dalwan01(a)student.umu.se) Review Manager - to be determined Download: Boost sandbox boost/named_params.hpp [and] libs/utility/doc/named_params.html Description: This library is an attempt to address the problems of positional parameters by associating each parameter with a keyword identifier. Using this library, users can identify parameters by name instead of just argument position, and pass them in any order: window* w = new_window("alert2", movable = movability, opacity = 50); October 6, 2004 Policy Pointer Author - David Held - dheld(a)codelogicconsulting.com Review Manager - to be determined Download: available via boost CVS Description: Smart pointers are used to automate memory management by handling the deletion of dynamically allcoated objects (and other resources). They assist in ensuring program correctness, exception safety, and memory integrity. Policy Pointer is a policy-based smart pointer framework designed to accomodate the large number of smart pointer designs. Through the use of policy classes, virtually any smart pointer type can be constructed within this framework. This library is a Boostification of the original Loki::SmartPtr type with significant modifications. October 16, 2004 Wave Author - Hartmut Kaiser - hartmutkaiser(a)t-online.de Review Manager - to be determined Download Boost-sandbox Description: The Wave C++ preprocessor library is a Standards conformant implementation of the mandated C99/C++ preprocessor functionality packed behind a simple to use interface, which integrates well with the well known idioms of the Standard Template Library (STL). It uses the Spirit[4] parser construction library to implement a C++ lexer with ISO/ANSI Standards conformant preprocessing capabilities. It exposes an iterator interface, which returns the current preprocessed token from the input stream. This preprocessed token is generated on the fly while iterating over the preprocessor iterator sequence (in the terminology of the STL these iterators are forward iterators). October 26, 2004 Finite State Machine (FSM) Author - Andreas Huber - ah2003(a)gmx.net Review Manager - to be determined Summary - not available Download - not available November 4, 2004 Fixed Strings Author - Reece Dunn - msclrhd(a)hotmail.com Review Manager - to be determined Download: boosts-sandbox/boost/fixed_string [or] boost-sandbox/libs/fixed_string Description: The fixed string library provides buffer overrun protection for static sized strings (char s[ n ]). It provides a C-style string interface for compatibility with C code (for example, porting a C program to C++). There is also a std::string-style interface using a class based on flex_string by Andre Alexandrescu with a few limitations due to the non-resizable nature of the class. Tom Brinkman Boost Review Wizard reportbase(a)yahoo.com

5 5

[multi_index] adding support for Compaq C++ for Tru64 Unix
by JOAQUIN LOPEZ MU?Z 21 Aug '04

21 Aug '04

Latest changes to Boost.Test have revealed that Boost.MultiIndex almost works for this compiler (toolset tru64cxx65), and I think the remaining problems are fixable. Is there any volunteer with local access to this compiler willing to help me in the process? Many thanks, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

regression in graph - brandes_betweenness_centrality_test
by Bronek Kozicki 21 Aug '04

21 Aug '04

There's memory access violation in brandes_betweenness_centrality_test.cpp . This error is thrown inside function put called in line 264 : for (tie(vi, vi_end) = vertices(g); vi != vi_end; ++vi) put(centrality, *vi, 0); // <<--- access violation inside put B.

1 0

numeric-ublas errors with Comeau
by Bronek Kozicki 21 Aug '04

21 Aug '04

All tests in numeric-ublas are failing in Comeau compiler. Most of these errors can be fixed if we define BOOST_UBLAS_NO_CMATH in boost/numeric/unblas/config.hpp for this compiler. Patch attached B. Index: boost/boost/numeric/ublas/config.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/numeric/ublas/config.hpp,v retrieving revision 1.36 diff -u -r1.36 config.hpp --- boost/boost/numeric/ublas/config.hpp 16 Aug 2004 05:31:03 -0000 1.36 +++ boost/boost/numeric/ublas/config.hpp 17 Aug 2004 22:12:08 -0000 @@ -33,6 +33,11 @@ #include <boost/type_traits/remove_reference.hpp> +// Comeau compiler +#ifdef __COMO__ +#define BOOST_UBLAS_NO_CMATH +#endif + // Microsoft Visual C++ #if defined (BOOST_MSVC) && ! defined (BOOST_STRICT_CONFIG)

1 1

Fw: Please Read: Boost Software License.
by John Maddock 21 Aug '04

21 Aug '04

And another permission: ----- Original Message ----- From: "Dan Gohman" <djg(a)cray.com> To: <boost-owner(a)lists.boost.org> Sent: Friday, August 20, 2004 9:21 PM Subject: Re: Please Read: Boost Software License. > I Dan Gohman, give permission for all my contributions to Boost to be > moved to the Boost Software License Version 1. > > On Thu, Aug 12, 2004 at 01:51:59PM +0100, John Maddock wrote: > > 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. > > > > As some of you will know already, in order to simplify Boost licensing, we > > are in the process of moving to a single common license > > (http://www.boost.org/LICENSE_1_0.txt) The aim of the new license is to > > provide a single wording, that encapsulates the our previous license > > requirements, and which will simplify the evaluation of Boost for commercial > > organisations. > > > > So here's the big question: may we have permission to change code that has > > your copyright to use the new license? Your copyright declaration would > > obviously remain, it's only the license text that would change. > > > > If "yes", and you have Boost-cvs write access, please add your name to > > more/blanket_permissions.txt. > > > > If "yes" and you have access to the Boost mailing list > > (boost(a)lists.boost.org) then please post a message there, subject "Boost > > License Permission", and content something like: "I Jim Hacker, give > > permission for all my contributions to Boost to be moved to the Boost > > Software License Version 1". (This gives us a public record that your > > permission has been given). > > > > If "yes", but you are no longer subscribed to the Boost list then please > > reply to boost-owner(a)lists.boost.org with content as above. > > > > If "no", please give us some idea what objections you may have. > > > > Finally, if this message was sent in error, please let us know, it's just > > about possible that we have you mixed up with someone of the same name, and > > if so apologies. > > > > Many thanks for your time, > > > > John Maddock. > > (Boost Moderator). >

1 0

Re: [boost] shared_ptr feature request: void_pointer_cast
by Jeff Williams 21 Aug '04

21 Aug '04

> Date: Thu, 19 Aug 2004 21:09:07 -0400 > From: "Joe Gottman" <jgottman(a)carolina.rr.com> > Subject: [boost] shared_ptr feature request: void_pointer_cast > > I know this isn't the best time to request a new feature, but I just had > an idea for an extremely useful new function for shared_ptr. It is common > to use a shared_ptr<void> in places where a void * would otherwise be used. > While a void * can point to anything, there is no safe way to determine at > run-time what type it originally pointed to. Casting it to the wrong type > can result in undefined behavior. How is this idea any different that just using boost::shared_ptr<boost::any> ? Jeff

2 1