- Boost - lists.boost.org

evc4 porting questions
by Michael Fink 05 May '06

05 May '06

Hi, I'm currently trying to port Boost to evc4 and while porting some questions arised that should be answered before. 1. There are some parts of the sourcecode where Ansi Win32-API-functions are used, e.g. CreateFileA. These are not supported under Windows CE. Some projects provided workaround when BOOST_NO_ANSI_APIS is defined and called e.g. the CreateFileW function instead. The functions often use std::string as parameters, and so string converting must be done. Now my question: is there a "best practice" way to do string conversions in Boost? Boost.Thread in one place uses the A2CW macro that comes from the ATL header atlconv.h to do string conversion (file boost/libs/thread/src/once.cpp). I had to include the necessary files at the top of this file to get it to compile. Is this the way it should be done on systems where ATL is available? 2. There are some parts in sourcecode where I have to do system-specific code for Windows CE. What is the preferred way to do that, introduce a BOOST_xx macro or use the one that is already defined by the compiler (that would be _WIN32_WCE). An example would be this: #if defined(__BORLANDC__) extern "C" BOOL WINAPI DllEntryPoint(HINSTANCE /*hInstance*/, DWORD dwReason, LPVOID /*lpReserved*/) #elif defined(_WIN32_WCE) extern "C" BOOL WINAPI DllMain(HANDLE /*hInstance*/, DWORD dwReason, LPVOID /*lpReserved*/) #else extern "C" BOOL WINAPI DllMain(HINSTANCE /*hInstance*/, DWORD dwReason, LPVOID /*lpReserved*/) #endif I guess as compiler-specific defines are used throughout the sourcecode, it's okay to use a macro like _WIN32_WCE. That's it. bye Michael

1 0

[MPL][pqs] best way to implement dimensional analysis
by David Abrahams 05 May '06

05 May '06

"Andy Little" <andy(a)servocomm.freeserve.co.uk> writes: > "Pedro LamarÃ£o" wrote > >> I would like to see some "motivating example", like this one from the >> MPL documentation: >> >> http://www.boost.org/libs/mpl/doc/tutorial/tutorial-metafunctions.html > > If the above is a motivating example for mpl It's not meant to be, really. It's designed to get the reader acquainted with the library's fundamental abstractions. > then I dont think it is the best one. It's true, but not for the reasons you suggest. The problem is that in this example there is no code generation, only typechecking, which makes it not a very good representative of what metaprogramming can do. > The problem is that mpl doesnt work as the (naive?) user expects, > but worse the actual type of the quantity resulting from a > multiplication isnt exactly defined. All that is known about it is > that its dimension is comprised of "some sequence". True. > In practise I found this, which was described as a convenience > feature Excuse me? Where did you _ever_ see this described as a convenience?! > actually caused a great deal more work in the implementation. It > also causes problems with trying to figure what to register with > Boost.Typeof and I suspect that it would continue to throw up > similar problems whenever the type is required to be known. The fact > is that an interface must have exactly predictable types. No, that is not a fact. You can find numerous examples in the standard (and more in TR1) where types are left unspecified. > The interface in this case ( The visible part. e.g for use in > function signatures etc) is in the template signature of the > class. IMO mpl isnt the best way to implement the dimension of a > quantity for this reason. If you mean that using mpl::transform on the builtin MPL sequences isn't the best approach, I'm inclined to agree. It's a somewhat naive approach designed to demonstrate some of the fundamental concepts in the library. I wouldn't agree if you were to suggest that MPL can't be useful anywhere in implementing such a library. > I am sorry to go on about this, Well, it is rather a strange outburst to find in the middle of the Fusion review thread, where someone just referred to the MPL doc to make a point. Maybe you should bring it up separately if you want to talk about this. -- Dave Abrahams Boost Consulting www.boost-consulting.com

2 1

[fusion] With or without qualification?
by David Abrahams 05 May '06

05 May '06

Are customizable fusion functions such as begin(s) supposed to be called with or without qualification? I.e. do you expect them to be found via ADL or by other means? -- Dave Abrahams Boost Consulting www.boost-consulting.com

2 1

Re: [boost] Deprecation and Boost
by Reece Dunn 05 May '06

05 May '06

Alisdair Meredith wrote: > > It has been agreed that several platforms will be deprecated in this > version of Boost. To support that I have added a warning to the > Borland config to alert anyone using old versions of this platform that > it is being deprecated and this is the last compatible release. > > What I notice is the warning gets annoying pretty quickly. > > I propose to wrap the warning in the following test: > > #if __BORLANDC__ <= 0x581 && !defined(BOOST_ACKNOWLEDGE_DEPRECATED_1_34) > # pragma message "..."; > #endif > > This will allow users to disable the warning by defining the macro in > their environment. It may be useful to make it work the other way (learning from Microsoft deprecating features by default). If not, then tell the user how to turn the deprecation off in the message, e.g. The Borland compiler for versions lower than 6.0 are deprecated. Support for this platform will be dropped in the future. To turn off this warning, define .... > I would like to extend this to a general policy, to make deprecation > more visible were it occurs. Using the BOOST_ACKNOWLDGE_DEPRECATED > test we could deprecate libraries or functions, as well as platforms. That would be useful, but see above. > The test is a simple 'does this macro exist' rather than testing for a > value, so should be compatible with toolchains that allow defining > macros, but not giving them values. Agreed. > The macro is tied to the specific version that is deprecated, so in > later releases we should grep for BOOST_DEPRECATED and either update > the version, or do something stronger such as use #error (platform) or > remove the code entirely (library) Maybe have a BOOST_FORCE_DEPRECATE_AS_ERROR macro to use errors instead of warnings, but using warnings by default. > If this meets approval I will try to write up some more formal > documentation for early next week, and provide something for the 1.34 > release notes. Great. > For reference I believe we agreed to deprecate the following platforms > in this release: > borland < 5.8 [Recommend we only support 5.82] > gcc 2.95 > MSVC < 7.1 > CW 8.3 I would say CW <= 8.3 if users have 8.2 or earlier. - Reece _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

1 0

[Boost-bugs] [ boost-Feature Requests-1482308 ] filesystem::path as a template
by SourceForge.net 05 May '06

05 May '06

Feature Requests item #1482308, was opened at 2006-05-05 12:53 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1482308&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Raider (streetraider) Assigned to: Nobody/Anonymous (nobody) Summary: filesystem::path as a template Initial Comment: I suggest boost::filesystem::path to be a template: template <typename CharType = char> class path; Current path will be used as path<char>. Of course it's unable to use path<wchar_t> for file operations like open(), rename() and so on with current C++ library. These function may take path<char> as parameters. But it's very useful to have path<wchar_t> dealing with filenames! Any will be able to use it and pass them for WinAPI functions by example, or use in any database that support wide chars. At second, I think path::extention() member function will be useful to exctact extention of the file, such as ".html" (or just "html") for "foo/bar.html". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1482308&group_… ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[thread] Patch for BCB2006
by Nicola Musatti 05 May '06

05 May '06

Hallo, if nobody objects I plan to commit the attached patch in a couple of days. It just extends the existing workaround to the latest compiler release. Cheers, Nicola Musatti ******Index: read_write_mutex.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/thread/read_write_mutex.hpp,v retrieving revision 1.9 diff -d -u -r1.9 read_write_mutex.hpp --- read_write_mutex.hpp 11 Jul 2005 15:06:07 -0000 1.9 +++ read_write_mutex.hpp 2 May 2006 20:59:52 -0000 @@ -53,7 +53,7 @@ typedef detail::thread::scoped_timed_lock<Mutex> scoped_timed_lock; read_write_mutex_impl(read_write_scheduling_policy::read_write_scheduling_policy_enum sp); -#if !BOOST_WORKAROUND(__BORLANDC__,<= 0x564) +#if !BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT(582)) ~read_write_mutex_impl(); #endif ******Index: read_write_mutex.cpp =================================================================== RCS file: /cvsroot/boost/boost/libs/thread/src/read_write_mutex.cpp,v retrieving revision 1.23 diff -d -u -r1.23 read_write_mutex.cpp --- read_write_mutex.cpp 27 Aug 2005 10:25:15 -0000 1.23 +++ read_write_mutex.cpp 2 May 2006 20:59:40 -0000 @@ -379,7 +379,7 @@ , m_readers_next(true) {} -#if !BOOST_WORKAROUND(__BORLANDC__, <= 0x564) +#if !BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT(582)) template<typename Mutex> read_write_mutex_impl<Mutex>::~read_write_mutex_impl() {

2 2

[SoC] Applicaton License.
by Giovanni P. Deretta 05 May '06

05 May '06

Hello all, In Google SoC FAQ, it is explicitly stated that any project developed during the SoC must be covered by a OSI approved license. AFAIK the boost license has not been approved (nor has never been proposed for approval). Could this be a problem, considering that projects developed under boost mentoring are likely candidates for boost inclusion? Should google be asked to make an exception for the Boost licence? Should projects be released under dual licensing (for example a OSI license like BSD + the Boost license)? --- Giovanni P. Deretta

3 3

[SoC] More Ideas
by Andrey Ryabushenko 05 May '06

05 May '06

I have some ideas in the field of my specialty - memory management. I can develop any of these with pleasure. But I want to hear from you which are most wanted or unwanted:) I can't write three great proposals at the same time so I am asking you. 1. Garbage collector. Smart pointers are great, but there is easier solution that do not require neither special knowledge nor available code modification. 2. Memory Leak Detector. Very helpful in big projects. It is worth to say that 70-80 percent of mistakes is memory leakage. 3. Develop a suite of allocators(multi threaded, small object allocator and others). I think the allocator based on Hoard algorithm that shows great perfomance in the multithreaded applications is worth merging into boost) take a look at more detailed descriptions www.cs.umass.edu/~emery/pubs/berger-asplos2000.pdf http://developers.sun.com/solaris/articles/multiproc/multiproc.html Please let me know if you have any interest in these topics.

2 1

[Boost-bugs] [ boost-Bugs-1482220 ] "memory exhausted" in regex matching
by SourceForge.net 05 May '06

05 May '06

Bugs item #1482220, was opened at 2006-05-04 17:46 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=1482220&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: regex Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: John Maddock (johnmaddock) Summary: "memory exhausted" in regex matching Initial Comment: Using the following regex: (a*ba*)*c to match the following text: abababababababababababab will throw an exception saying "Memory exhausted" (tried with g++ 4.0.4 on linux with boost 1.32 and 1.33. Similar problem on Windows/mingw with 1.32) The following, more useful expression has the same problem: (a*ba*d?)*c Charles-Henri Gros <chgros(a)coverity.com> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1482220&group_… ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[MPL] sequence-preserving
by David Abrahams 04 May '06

04 May '06

Joel de Guzman <joel(a)boost-consulting.com> writes: > So MPL is not sequence preserving after all. It really depends what you mean by "sequence preserving." If it returned the same type, it couldn't really do anything. So you have to decide how many guarantees you're going to give about the result type. Andy wants it to be spelled as a specialization of the same template, so transform operating on mpl::vector<t1,t2,t3> would yield something spelled mpl::vector<t1a,t2a,t3a>. > transform merely returns a sequence with the same properties as the > original. This makes perfect sense. In Fusion, algorithms are not > sequence preserving by design. However, we do have conversion > functions/metafunctions to get a *true* vector/list/set/map from an > arbitrary sequence. No, I don't think that would satisfy Andy, because you're surely not guaranteeing that the result type will be spelled fusion::list<t1,t2,t3,...> or you wouldn't be able to do this to lists of arbitrary length (and why else use a list, after all?). You probably have to conjure up something spelled cons<t1,cons<t2,cons<t3,nil> > >, which, while it's a "true list", it isn't a specialization of fusion::list. Which leaves fusion right back in the same place as MPL. Unless I'm missing something, of course ;-) -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0