April 2005 - Boost - lists.boost.org

Re: [boost] Visual Studio 2005 Beta 2 + Multi Index
by JOAQUIN LOPEZ MU?Z 09 May '05

09 May '05

----- Mensaje original ----- De: Gordon Smith <schmoo2k(a)hotmail.com> Fecha: Viernes, Abril 22, 2005 5:43 pm Asunto: [boost] Visual Studio 2005 Beta 2 + Multi Index > The following stdafx.h for a vanilla console app kills the beta 2 > compiler > (I think it creates a corrupt PCH file): > > #pragma once > > #define WIN32_LEAN_AND_MEAN // Exclude rarely-used stuff from > Windows > headers > #include <windows.h> > #include <tchar.h> > > // BOOST --- > #include <boost/multi_index/sequenced_index.hpp> > #include <boost/multi_index/ordered_index.hpp> > Hi Gordon, excuse my late answering, somehow I just didn't see your post amidst the current flow of messages. Did this work for MSVC 8.0 beta 1? I'm afraid I cannot help much here except suggest that you try to report this to the MSVC dev team: http://lab.msdn.microsoft.com/productfeedback/ Also, please try deleting all intermediate files before doing a fresh compile --this is sometimes helpful specially in regard to PCHs. If you make any progress or need some help please keep me informed. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 2

RE: [boost] Logging Library -- Formal Review Request
by Roman Yakovenko 08 May '05

08 May '05

John Torjo wrote: > > I've just updated the Boost Log Library: > http://torjo.com/code/logging-v132.zip > > > I would also like to ask for a _Formal Review_. > > > > The Boost Log Library is a small library, who: > * makes it very easy to declare/define new logs > * allows you very simple access to logs > * allows for log hierarchies, and for modifying log hierarchies > * allows for easy and efficient enabling/disabling of > logs/log hierarchies > * allows for easy manipulation of log behaviors > (the log's destination(s) and/or adjusting the original message) > * is thread-safe > > Using the library in code is easy and straightforward: > > int i = 1, j = 2, k = 3; > BOOST_LOG(app) << "testing " << i << '-' << j << '-' << k << > std::endl; > BOOST_LOG(dbg) << "this is a debug message, i=" << i << std::endl; > BOOST_LOG(info) << "I just wanted to tell you something...."; > Hi. If I understand right the code, even if log is disabled, I do pay for constructing log messages. Am I right? If so why do you force this? Roman

13 22

[test] PATCH: putenv usage incorrect
by Caleb Epstein 06 May '05

06 May '05

http://tinyurl.com/72sj8 This test is failing on numerous platforms, some for the fact that "putenv" takes a non-const char* (Linux, Solaris, perhaps others). Attached is a patch for environment.ipp which changes it to use the setenv function on non-Windows systems. I believe this is a POSIX standard function (via BSD). I think this cleans up the code a bit, removing the raising of getenv/putenv into namespace std, when they are I think clearly non-std functions. -- Caleb Epstein caleb dot epstein at gmail dot com

3 6

(Another) socket streams library
by pedro.lamarao＠mndfck.org 05 May '05

05 May '05

Hello, all. I see everybody has been talking about a networking library for a long while. Checking the wiki, I see that my own project has escaped attention. So, here it goes for the examination of the experts: http://socketstream.sourceforge.net/ -- Pedro Lamarão

11 47

[thread] warnings with CW 8.3
by Bertolt Mildner 05 May '05

05 May '05

when building boost.thread (from public CVS / HEAD) with CW 8.3 i get the following warnings: ... cw-C++-action ..\..\..\bin\boost\libs\thread\build\libboost_thread.lib\cw\debug\ threading-multi\read_write_mutex.obj ### mwcc Compiler: # File: ..\src\read_write_mutex.cpp # ------------------------------------ # 934: } # Warning: ^ # return value expected ### mwcc Compiler: # 1163: } # Warning: ^ # return value expected ### mwcc Compiler: # 1247: if (woken = do_wake_all_readers()) # Warning: ^ # possible unwanted assignment ### mwcc Compiler: # 1253: if (woken = do_wake_writer()) # Warning: ^ # possible unwanted assignment ... Bertolt

2 4

Intrusive containers: second iteration
by Olaf Krzikalla 04 May '05

04 May '05

Hi, the second version of intrusive containers is available. Excerpt from the introduction: ---snip--- Welcome to Boost.Intrusive, a library presenting some intrusive containers to the world of C++. While intrusive containers were and are widely used in C, they became more and more forgotten in the C++-world due to the presence of the standard containers, which don't support intrusive techniques. Boost.Intrusive not only reintroduces this technique to C++, but also encapsulates the implementation in STL-like interfaces. Hence anyone familiar with standard containers can use intrusive containers with ease. ---snap--- You find the file intrusive.zip either in the yahoo file section or here: http://people.freenet.de/turtle++/intrusive.zip I consider this version being rather complete now and quite ready for a formal review (barring islist maybe). Best regards Olaf Krzikalla

8 24

boost::regex (sub_match), regex string that matched?
by Preston A. Elder 04 May '05

04 May '05

Hi, Is there a way to find out either the string, begin/end iterator or even the position of the regex string that created a sub_match? Lets say I have a regex parser that allows a dynamically defined regex to be passed (say, user defined, from a config file). So A user might pass: Bla (.*) blerk (.*) ([[:digit:]]+) Bla .* ([[:alpha:]]*) Or pretty much any regex (actually, in my case, this is not completely true, however lets just say for argument's sake ...). Now assuming another arbitary string is passed to this function, and it matches the user-passed regex. How do I find out what the REGEX was that matched this particular sub_match (or the position in the passed regex). For example, if the second regex above was passed, I know by looking at it that matches[1] was 'created' by ([[:digit:]]+) and matches[2] was 'created' by ([[:alpha:]]*). However programatically, I cannot find out. Why can sub_match not include a mfirst and msecond parameter (and mstr() function), that like first and second (and str()), will point to the beginning and end, but of the regex string instead of the 'input' string. -- PreZ :) Founder. The Neuromancy Society (http://www.neuromancy.net)

2 1

How do I show entire compiler command line when building boost
by dennisct＠fastmail.fm 04 May '05

04 May '05

Hi, I think this is a very simple question, but I can't find the answer in the boost.build or boost.jam documentation... Is there any way I can make the boost build system show the entire command line (including compiler specific options/flags) it uses to compile files and build libraries? I'm having problems with the new serialization library not linking to the right runtime on vc71 and I'd like to see that command line. By default, it seems to only print the name of the compiler it is using. Regards Dennis

3 3

DLL/SO loading library.
by Vladislav Lazarenko 03 May '05

03 May '05

Greetings, dear developers. I have some simple idea to write platform independed library to provide users with ability to load DLL/SO files (i.e. to develop plugin system etc.). Is there any library in boost? I've found nothing. Maybe we need it? Let's discuss, I am interested in your comments. Thank you very much in advance.

14 32

[Filesystem] i18n
by Martin 02 May '05

02 May '05

Didn't find any comments on the new filesystem implementation so here are mine - Would it be possible to store the new files in the vault? I find it inconvenient to check out a special branch just to read the documentation. - I haven't compiled the new files but I have had a good look at the documentation and the source. My impression is that it is a very nice implementation. (All the #ifdefs make the source hard to follow but I'm not the maintainer) - Specially I like the switch from default portable syntax to default native syntax. It means that I no longer need to change the default name checker in each application and that the "native_" prefix from the access functions are gone. (Maybe the name checker could be a template parameter (with default "none") for those who still want to use it. Would complicate implementation of operations.) The comments I have on the new implementation is: - Operations are limited to std::string (and std::wstring on win32) as external type. Why not allow any range of characters? Current implementation will not work with const_string, flex_string and a basic_string with a custom allocator. - Why not have a static locale member in the class instead of using the utf-8 facet. The locale could then be used both for internal/external conversion via the codecvt facet and get operator< to work with a custom locale. (for posix the locale would default to locale::global() with the utf-8 facet added) I also had hopes for some new things that didn't appear in the new implementation. - non-throwing is_* functions. I find it very inconvenient and error prune to put try/catch around each is_directory call. Calling is_accessible before every other is_* function is an option but not much easier and still leaves a risk for an exception if another process is accessing the file. The throwing is_* functions also makes it impossible(?) to use the directory iterator with algorithms like remove_copy_if(directory_iterator(path), directory_iterator(), back_inserter(filelist), is_directory) My suggestion is to add non-throwing overloads where a second parameter tells what the function should return in case of error. e.g. is_directory(path, true). - The directory iterator is still very limited since you can't specify a filter (e.g. "*.txt"). If used on a win32 system with a mounted posix disk or a posix system with a CD problems might arise. (There is no portable way to tell if "FILE.TXT" matches "*.txt"). - Why doesn't last_write_time return a boost::ptime

7 38