- Boost - lists.boost.org

STLport builds
by Valentin Samko 08 Jun '05

08 Jun '05

I've been trying to build Boost.Thread and a number of other libraries for use in the software in the company where I work, and was only stopped by a number of STLport related problems. We already use header-only boost libraries for many years, and now would like to start using other boost libs. The main problems are: 1. We use unchecked STLport variant (i.e. without __STL_DEBUG). Unfortunately, Boost is not compatible with this mode, although a fix to add this mode is only a few lines of code in boost build. When I added this mode and recompiled boost, everything ran without any noticeable problems. I think it is worth adding this mode to boost build so that developers wouldn't have to patch boost build to add this mode. 2. It is very usefull that compiled boost libraries embed version number and different compile time options in their names. Unfortunately, STLport version is not embedded in their names (only 'p'). This creates a problem where two executables compiled against different STLport versions try to use the same Boost.WhateverLibrary dll. Are there any reasons not to embed STLport version number into boost library names? 3. A separate issue with Boost.Threads, where _sntprintf is called in boost_error in read_write_mutex.cpp, even when building with STLport, which does not have _snprintf. Also, there is bug in boost_error, which wrongly assumes that _sntprintf zero terminates the resulting string. I also wrote a patch to fix this problem. Is there any way to merge it into Boost.Thread? I understand that we could solve these problems either by not using STLport, or by changing the way we use it, but unfortunately, this is next to impossible for us, as we have a large software suite which is built and supported this way for years. Also, I think other developers would benefit if Boost provided workarounds/solutions for these common STLport problems. -- Valentin Samko http://val.samko.info

3 3

RE: [boost] Re: Kinook is using boost
by Brian Braatz 08 Jun '05

08 Jun '05

HAHAHAh When I clicked on the link earlier I was thinking the same thing. >From what I could gather on their web page- this is a commercial app that is closed source. > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Robert Ramey > Sent: Tuesday, June 07, 2005 6:46 PM > To: boost(a)lists.boost.org > Subject: [boost] Re: Kinook is using boost > > Hmmm - any chance it could build the boost libraries and run the tests? > > Robert Ramey > > Kyle Alons wrote: > > Kinook Software (http://www.kinook.com) uses Boost in the following > > products: > > > > Product: Visual Build Professional > > Description: Visual Build Pro is a tool that enables developers, > > software process engineers, and build specialists to create an > > automated, repeatable process for building their software. Visual > > Build provides built-in support for Microsoft Visual Studio .NET and > > 2005, Visual Basic, Visual C++, Visual J++, SourceSafe, eMbedded > > Tools, Borland Delphi, JBuilder, C++Builder, and more. > > Parts of Boost used: any, mem_fn, regex, shared_ptr, smart_ptr, > > static_assert > > Web site: http://www.visualbuild.com/ > > > > Product: Ultra Recall > > Description: Ultra Recall is a personal information management (PIM) / > > knowledge management (KM) application for Microsoft Windows. It helps > > you capture, organize, and recall all of your electronic information > > across all the applications that you use. > > Parts of Boost used: format, shared_ptr, static_assert > > Web site: http://www.ultrarecall.com/ > > > > Thanks. > > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Kinook is using boost
by Kyle Alons 08 Jun '05

08 Jun '05

Kinook Software (http://www.kinook.com) uses Boost in the following products: Product: Visual Build Professional Description: Visual Build Pro is a tool that enables developers, software process engineers, and build specialists to create an automated, repeatable process for building their software. Visual Build provides built-in support for Microsoft Visual Studio .NET and 2005, Visual Basic, Visual C++, Visual J++, SourceSafe, eMbedded Tools, Borland Delphi, JBuilder, C++Builder, and more. Parts of Boost used: any, mem_fn, regex, shared_ptr, smart_ptr, static_assert Web site: http://www.visualbuild.com/ Product: Ultra Recall Description: Ultra Recall is a personal information management (PIM) / knowledge management (KM) application for Microsoft Windows. It helps you capture, organize, and recall all of your electronic information across all the applications that you use. Parts of Boost used: format, shared_ptr, static_assert Web site: http://www.ultrarecall.com/ Thanks. -- Kyle Alons Kinook Software, Inc. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

RE: [boost] Re: [function types] Formal Review begins today.
by Brian Braatz 07 Jun '05

07 Jun '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Jody Hagins > Sent: Tuesday, June 07, 2005 8:49 AM > To: boost(a)lists.boost.org > Subject: Re: [boost] Re: [function types] Formal Review begins today. > > > > Seems like we have a fundamentally different taste when it comes to > > documentation... [Jody Hagins Writes:] > > Probably. > [Brian Braatz Writes:] Allow me to suggest 2 ways of thinking about library documentation: 1- The better the documentation is, and the more it speaks to the average user, the more usage the library will have. If the docs don't make sense, people will SKIP using the lib. (which is a shame) 2- The lower the skills required of the reader the better. I realize one can only do so much in documentation. I am simply stating that the simpler and more understandable the docs are the better. This is because the "skilled" folks can skip the intro if it is obvious. I believe: "Brilliance is a mastery of the obvious" <*>>> and documentation should seek to brilliantly expose the obvious over complicated subjects.

3 2

RE: [boost] Re: [function types] Formal Review begins today.
by Brian Braatz 07 Jun '05

07 Jun '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of David Abrahams > > > > "Brilliance is a mastery of the obvious" <*>>> and documentation should > > seek to brilliantly expose the obvious over complicated subjects. > [David Abrahams Writes:] > Another thing: the author of documentation should (usually) disqualify > him- or herself from making judgements about understandability and > especially approachability. The problem is that once you understand > it, it's very hard to see the places where it fails to communicate to > someone who doesn't. [Brian Braatz Writes:] :) " The problem is that once you understand > it, it's very hard to see the places where it fails to communicate to > someone who doesn't." A RESOUNDING YES!!!!!!- And thank you David. This sentence is worthy of printing out and hanging on my wall. Or maybe I should make tee-shirts and hand them out at conferences. Or better yet, I could have stickers made and hand those out. Then anytime someone sees some documentation that fails to make sense to normal humans, they can slap the sticker on it and hand it back to the author.

1 0

boost cvs build failure: Unknown suffix
by Neal Becker 07 Jun '05

07 Jun '05

PYTHON_ROOT=/usr PYTHON_VERSION=2.4 bjam -sTOOLS=gcc stage Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). Unknown suffix on <@boost!libs!iostreams!build><<<<<<< - see UserObject rule in Jamfile(5).

1 1

[cvs] waiting for lock
by Pedro Lamarão 07 Jun '05

07 Jun '05

TortoiseCVS, while trying to update a working copy, has been telling me for more than an hour that it's "waiting for david_abrahams's lock in /cvsroot/boost/boost/libs/preprocessor/doc/headers/control". I'm not sure what that means besides me being currently incapable of cvs update. I'll keep trying for a while. -- Pedro Lamarão Desenvolvimento Intersix Technologies S.A. SP: (55 11 3803-9300) RJ: (55 21 3852-3240) www.intersix.com.br Your Security is our Business

2 2

Liquidnet is using boost
by Max Khesin 07 Jun '05

07 Jun '05

Ok, I've been waiting to say this :-), thanks for putting this page together John! Liquidnet, a financial startup and last 5th fastest growing company according to Inc is using Boost. Libraries most used, in order of importance (as if I can really measure that): shared_ptr bind boost.python lexical_cast optional any tuple regards and keep up the great work, max. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

1 0

[Iostreams] Fails to build on Windows
by Keith MacDonald 07 Jun '05

07 Jun '05

At the time of writing, Iostreams from CVS head still does not build on Windows XP, due to missing header files. The build starts with these comments: ****************************************************** Building Boost.Iostreams with bzip2 support disabled. HINT: define the environment variable BZIP2_SOURCE to point to the root directy of your bzip2 installation if you have one. For more options, consult the Boost.Iostreams documentation ****************************************************** ****************************************************** Building Boost.Iostreams with zlib and gzip support disabled. HINT: define the environment variable BZIP2_SOURCE to point to the root directy of your zlib installation if you have one. For more options, consult the Boost.Iostreams documentation ****************************************************** Presumably "BZIP2_SOURCE" should not effect both types of compression, and "directy" is a typo. Anyway, the following errors are then reported 8 times each: bzip2.cpp(14) : fatal error C1083: Cannot open include file: 'bzlib.h': No such file or directory zlib.cpp(14) : fatal error C1083: Cannot open include file: 'zlib.h': No such file or directory The command line I used for the build was: bjam -sTOOLS=vc-8_0 -sICU_PATH=F:\Dev\icu-3.2 -sPYTHON_ROOT=C:\Apps\Python24 -sPYTHON_VERSION=2.4

3 8

RE: [boost] Re: [function types] Formal Review begins today.
by Brian Braatz 07 Jun '05

07 Jun '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Jody Hagins > > Well, in case you don't know MPL (although the primary audience most > > likely will) you can still have a look at the synopsis and look for > > the version with non-type template parameter... > > I would disagree with you here. Many boost users do not know MPL. Many > more probably have a cursory knowledge of MPL, but still need > documentation handy to make use of it. > > > > How do functors fit in here? If a class overloads operator(), is it > > > considered a function type? > > > > > > No. Is the definition really that unclear ? > > > > How could this probably work if operator() is a function template ? > > > > You can decompose a member function pointer to a parentheses operator > > (which implies it's already instantiated if it's a template > > function), though (after deduction or using some kind of typeof > > operator). > > No, it is clear, but I would think that some notes about operator(), > boost::function, and boost::lambda would be appropriate, since some > folks may want to use them in some ways related to function_types. > > > > > knowledge of the MPL. However, the docs seem to take too much for > > > granted, and make too many assumptions. I'd like to see more > > > detail, especially in the descriptions. > > > > What do you mean with "assumption" ? Preconditions on template > > arguments ? > > I think interface documentation should make the lowest common > assumptions. Not everyone is familiar with the types of problems this > library is trying to solve. I am sure you are not merely targeting an > audience of people who could implement this library themselves, but > those who would like this functionality without implementing the > details. > > FWIW, most boost libraries fail in this regard, in my opinion. Library > documentation should make as few assumptions about the knowledge and > experience of the user as possible. > [Brian Braatz Writes:] THANK YOU JODY- I was going to say that (grin). Allow me to add a suggestion. PICK YOUR TARGET person's skills. And then write your docs to that person. I would advocate - if you can pull it off- think about someone you know who has 2-3 years CPP experience. Think about how you would communicate your library to that person. Walk them through using the library and solving problems with the library. Assume the user knows VERY LITTLE about metaprogramming etc. Hope that helps, and thank you Jody for spending the time to write up your feedback :)

1 0