Re: [boost] "Software Development using the C++ Boost Library", book in preparatiion

Subject: Re: [boost] "Software Development using the C++ Boost Library", book in preparatiion
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-02-17 07:04:49

Daniel J. Duffy wrote:

This thread is disturbing; read on.

> 1. Phoenix: I'm sold :-) This will be a great library for
> applications. The chapter we had for Lambda is now for
> Phoenix. Nice that it can be used as a separate module. Maybe
> it should be a 1st-class library in its own right?

I believe Joel already said it would be in v3.

> 2. type erasure: I looked this term up but it seems as if it
> is similar to interface/device independent/ programming. In
> the past we built homemade Function and used it in
> combination with OO specialisation with virtual functions,
> Now boost Function is so much better. Mathematicians and
> engineers are used to functions and we adopt the same
> approach (e.g. using namespaces)

It seems troublesome that you would assert authority to write about a wide array of the more advanced Boost libraries without knowing the meaning of "type erasure."

> 3. Ideally, we would like TR1 and boost to be as seamless as possible.

That's rather vague.

> 4. Fusion: I think this is useful, especially with Any?

I realize that you just learned of this library, so you can't speak from firsthand or specific knowledge, but that, itself, is disturbing based upon the original message in this thread in which you stated that the book is "in preparation," that it "is pitched" to certain skill levels, etc., which suggested you had already written much of the book.  At this point, one easily can conclude that you have only conceived the book idea, possibly even pitched it to a publisher, and now want to know what to put in it, all while having only a cursory knowledge of Boost.

> 6. "Boost Library"; there are many libraries in the
> collection, What is the best description: "Boost", "Boost
> Suite" when referring to everything?

You claim some subject matter authority, given that you intend to write a book on numerous libraries from Boost, and yet you apparently don't know enough about the community to find the home page.  The logo in the upper left corner uses the phrase "Boost C++ Libraries," and the first sentence states that, "Boost provides free peer-reviewed portable C++ source libraries."  Later sentences use the phrase "Boost libraries."  The home page should give you what you need to know how to refer to Boost and its libraries.  That you didn't investigate that far is disturbing.

There are a number of books that mention Boost, including _Beyond the C++ Standard Library: An Introduction to Boost_, by Bjorn Karlsson, which should have demonstrated how to reference the libraries.  Have you read the extant books on or related to Boost?

There have even been discussions in this mailing list on that subject.  Did you search for them?

I'm not against the idea of your book or of your writing it, but it seems as though you are asking us to critique the initial outline, suggest what you should write about, provide examples, etc., all before you've done the research needed to know the Boost libraries and community.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.