- Boost - lists.boost.org

Re: [boost] Re: Another logo proposal
by JOAQUIN LOPEZ MU?Z 22 Nov '04

22 Nov '04

----- Mensaje original ----- De: Daniel Frey <d.frey(a)gmx.de> Fecha: Lunes, Noviembre 22, 2004 11:43 pm Asunto: [boost] Re: Another logo proposal > JOAQUIN LOPEZ MU?Z wrote: > > You mean, like the version attached? > > I don't know, it kind of looks too irregularly shaped. Not > > so blocky as the other designs. > > Hm, no offense intended, but this logo seems more appropriate for > a > mortician. YMMV. :) > LOL :) What do you make of this, then? http://tinyurl.com/59y5z Best, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

Re: RE: [boost] Another logo proposal
by JOAQUIN LOPEZ MU?Z 22 Nov '04

22 Nov '04

----- Mensaje original ----- De: Robert Geiman <rgeiman(a)buckeye-express.com> Fecha: Lunes, Noviembre 22, 2004 11:49 pm Asunto: RE: [boost] Another logo proposal > Yes, I like the simplicity a lot. However, I'd also make a slight > change to the background of the ++. Could you remove the lower right > background of the ++, and instead mirror the upper left background > vertically. That is, the background would appear in the upper and > lower left area of the ++. > > To me this would look better as the background would look like the > letter C, which would go nicely with the ++. > I think this is what you've got in mind. Myself, I don't like it much. Not so compact, and the "C++" thing becomes too obvious. But well, this is just my opinion, of course. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

Re: [boost] Re: Another logo proposal
by JOAQUIN LOPEZ MU?Z 22 Nov '04

22 Nov '04

Hi Rich ----- Mensaje original ----- De: Rich Johnson <rjohnson(a)dogstar-interactive.com> Fecha: Lunes, Noviembre 22, 2004 8:57 pm Asunto: Re: [boost] Re: Another logo proposal > > I like the stair-step imagery of the second .png- (the one with no > backing field) > It's a nice play on the use of building blocks. I think it still > carries a blocky, solid/stable feel. > > Is there a single color restriction for ease of printing? If not > adding a third '+' in a different color (or perhaps in outline) > would > further emphasize building on C++. You mean, like the version attached? I don't know, it kind of looks too irregularly shaped. Not so blocky as the other designs. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 2

boost.thread : Can one create a thread with an object member function?
by Tim Laplaca 22 Nov '04

22 Nov '04

I am very new to boost, I apologize if this has been asked before. I searched the mailing list archive but could not find an answer to my question. I was successful creating threads with functions that are not members of objects, but when I try to create threads with a pointer to an object member I get compilation errors (MS Visual Studio .NET). Examples: class objclass; typedef void (objclass::*pmf)(); // ptr to member func class objclass { public: objclass() : thread_id (0) { p=&objclass::dowork; } inline setthreadid(int x) {thread_id = x;} inline setvaltwo(std::string str) {valtwo = str;} void dowork(); pmf p; // pointer to dowork member function int getthreadid() {return thread_id;} std::string getvaltwo() {return valtwo;} private: int thread_id; std::string valtwo; }; void objclass::dowork() { } (In the main...) boost::thread_group thrds; objclass * objthread; objthread = new objclass; thrds.create_thread( (objthread->p) ); I get the following error: c:\Boost\include\boost-1_31\boost\function\function_template.hpp(427): error C2664: 'void boost::function0<R>::assign_to<Functor>(FunctionPtr,boost::detail::funct ion::function_ptr_tag)' : cannot convert parameter 2 from 'boost::detail::function::member_ptr_tag' to 'boost::detail::function::function_ptr_tag' with [ R=void, Functor=pmf, FunctionPtr=pmf ] Is there a way around this problem, or is it simply not possible to make threads from object members with boost? Thanks, Tim

3 2

RE: [boost] Another logo proposal
by Robert Geiman 22 Nov '04

22 Nov '04

---- Original Message ---- From: joaquin(a)tid.es To: boost(a)lists.boost.org Subject: RE: [boost] Another logo proposal Date: Mon, 22 Nov 2004 16:49:12 +0100 >Here's my take. I'm providing b/w and color versions. The idea >is to provide an abstract logo to associate with Boost while >retaining >the visual link with the previous artwork (through using the same >Impact font for the name, a very appropriate font IMHO.) >Some more rationales behind the proposal: > >* It can be easily rasterized. >* It goes well with flat backgrounds. >* It works as a transition from the old logo. > >As for the logo itself, it tries to convey the following >connotations: > >* Its square shape, and the fact that is bottom aligned >with the text, gives a sense of solidness. >* It reminds the reader of a set of construction toolkit >pieces, which associates well with Boost being a repository of >general purpose libraries. >* The "++" part of C++ is retained, integrated into the >logo. Going a little pedantic, one can even recognize >the logo as a deconstruction of "C++", where the L-shaped >pieces are the two halves of an upper "C", split and shifted. > >Dya like it? Yes, I like the simplicity a lot. However, I'd also make a slight change to the background of the ++. Could you remove the lower right background of the ++, and instead mirror the upper left background vertically. That is, the background would appear in the upper and lower left area of the ++. To me this would look better as the background would look like the letter C, which would go nicely with the ++. - Robert Geiman

1 0

[serialization] std::set compile errors
by Jeff Flinn 22 Nov '04

22 Nov '04

Robert, boost 1.32, with VC7.1 I'm getting compiler errors in two unrelated translation units both dealing with std::set<std::string> data members. I've gone through and ensured that i've #include'd the <set.hpp> and <string.hpp> headers from boost/serialization. Any ideas on what might be causing this problem? This has worked fine previously with boost 1.31 and serialization20 version of the library. Why would the 3 argument overload not be found? Below are the (beginnings of the ) related compiler errors. Thanks, Jeff ======================== C:\boost\boost_1_32_0\boost\serialization\split_free.hpp(55) : error C2780: 'void boost::archive::load(Archive &,T &)' : expects 2 arguments - 3 provided C:\boost\boost_1_32_0\boost\archive\detail\iserializer.hpp(514) : see declaration of 'boost::archive::load' C:\boost\boost_1_32_0\boost\serialization\split_free.hpp(54) : while compiling class-template member function 'void boost::serialization::free_loader<Archive,T>::invoke(Archive &,T &,const unsigned int)' with [ Archive=boost::archive::text_iarchive, T=std::set<std::string> ] .... ======================== C:\boost\boost_1_32_0\boost\serialization\split_free.hpp(55) : error C2780: 'void boost::archive::load(Archive &,T &)' : expects 2 arguments - 3 provided C:\boost\boost_1_32_0\boost\archive\detail\iserializer.hpp(514) : see declaration of 'boost::archive::load' C:\boost\boost_1_32_0\boost\serialization\split_free.hpp(54) : while compiling class-template member function 'void boost::serialization::free_loader<Archive,T>::invoke(Archive &,T &,const unsigned int)' with [ Archive=boost::archive::binary_iarchive, T=std::set<std::string> ] ....

1 0

[serialization] and macro 'max' compiler warning on VC71
by Jeff Flinn 22 Nov '04

22 Nov '04

I've just tried to move to 1.32 and get the following warning: C:\boost\boost_1_32_0\boost\archive\basic_binary_oprimitive.hpp(101) : warning C4003: not enough actual parameters for macro 'max' which points to: assert( static_cast<std::size_t>(std::numeric_limits<std::streamsize>::max()) >= count ); Any suggestions on avoiding this with an MFC based project? Thanks, Jeff

3 4

[assign] documentation - bugs in examples
by Anton Gutsunaev 22 Nov '04

22 Nov '04

Some examples in <boost>/libs/assign/doc/index.html file print "Assertion failed" message or cannot be compiled. <boost>/libs/assign/doc/index.html#operator+= vector<int> values; values += 1,2,3,4,5,6,7,8,9; // insert values at the end of the container BOOST_ASSERT( values.size() == 9 ); BOOST_ASSERT( values[0] == 1 ); BOOST_ASSERT( values[9] == 9 );// <---must be "values[8]" <boost>/libs/assign/doc/index.html#operator() map<string,int> months; insert( months ) ( "january", 31 )( "february", 28 ) ( "march", 31 )( "april", 30 ) ( "may", 31 )( "june", 30 ) ( "july", 31 )( "august", 31 ) ( "september", 30 )( "october", 31 ) ( "november", 30 )( "december", 31 ); BOOST_ASSERT( m.size() == 12 ); //<---change "m" to "months" BOOST_ASSERT( m["january"] == 31 ); //<---same here after words "If operator()() is too cumbersome to use with eg. push_front()we can also say": deque<int> di; push_front( di ) = 1,2,3,4,5,6,7,8,9; BOOST_ASSERT( di.size() == 9 ); BOOST_ASSERT( di[8] == 9 );//<-- must be di[8]==1 or di[0]==9 because of push_front <boost>/libs/assign/doc/index.html#list_of: const stack<string> names = list_of( "Mr. Foo" )( "Mr. Bar")( "Mrs. FooBar" ).to_adapter(); const stack<string> names2 = (list_of( "Mr. Foo" ), "Mr. Bar", "Mrs. FooBar" ).to_adapter(); BOOST_ASSERT( names.size() == 3 ); BOOST_ASSERT( names[0] == "Mr. Foo" ); //<---can't use operator [] with stack BOOST_ASSERT( names[2] == "Mrs. FooBar" ); //<---same here example after words "A more general list can be constructed with repeat_fun()": template< class T > struct next { T seed; next( T seed ) : seed(seed) { } T operator()() const //<---remove const or declare "T seed" as mutable { return seed++; } };

2 1

[TYPO] Assignment Library
by Javier Estrada 22 Nov '04

22 Nov '04

Under the Reference section, the sentence: Originally const references was used, but it lead to many problems with string-literals. Should read: Originally const references were used, but it led to many problems with string-literals.

2 1

Typo in Assignment Library documentation
by Javier Estrada 22 Nov '04

22 Nov '04

In http://www.boost.org/libs/assign/doc/index.html there is a typo under the Introduction section. The sentence: These two operators makes it possible to construct lists of values which are then copied into a container: Should read: These two operators make it possible to construct lists of values which are then copied into a container:

3 2