- Boost - lists.boost.org

Re: [boost] Re: Standard C Library and C++ / BOOST
by Reece Dunn 30 Mar '04

30 Mar '04

Rob Stewart wrote: >From: "Reece Dunn" <msclrhd(a)hotmail.com> > > What about when you use boost::policy::errormsg_storage instead of > > boost::policy::no_errormsg_storage? Doing this allows the following: > > > > typedef boost::errorcheck< boost::policy::error_storage<>, > > boost::policy::errormsg_storage > > > errorcheckmsg; > > > > try > > { > > errorcheckmsg em; > > em( "oops!" ) = -3; // note the special syntax > > } > > catch( errorcheckmsg em ) > > { > > std::cout << "error: " << em.get_msg() << '\n'; > > } > > > > resulting in "error: oops!" being outputted. Using your method, the >message > > string will ont be passed and thus you would get "error: unspecified >error"! > > That is why I implemented it as above. > >I didn't see anything like that in the code you showed. It was >probably in the full implementation, but I was only looking at >what's quoted above. I posted it as a different message (errorcheck) and have been revising it based on comments and suggestions. The full code is attached here. >Anyway, why must either constructor manage the string at this >point? Why wouldn't the generation of the string occur at the >time it is requested? That is, there is no string to copy if >there is no string generated until the get_msg() mf is called. >That mf can create the string (reusing it if already computed, of >course). It depends on what you are using it for. The string for the errno handler *is* generated at get_msg() call-time. The above is based on an example Volodya posted where he put the name of the function he was calling into the code. E.g. // [paraphrased]: if( ::read( fn, ... ) < 0 ) report_error( "read", errno ); becomes ec( "read" ) = ::read( fn, ... ); As another example, you could have a handler that supports windows GetLastError and do something like: try { winerr( "Rectangle" ) = ::Rectangle( hDC, 10, 10, 110, 110 ); winerr( "Ellipse" ) = ::Ellipse( hDC, 10, 10, 110, 110 ); } catch( winapi_errorcheck e ) { std::cout << "error: " << e.get_msg() << " - " << e.error_string() << '\n'; } NOTE: I know that mixing GUI/console does not work -- this is just a usage demonstration. >If you find your approach is still needed, no problem. I just >wanted to be sure you understood what I had implied. No worries. I understood your approach, but I was designing it to be as flexible as possible. Regards, Reece _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger

1 0

Building bcp with Jam V2 and como
by Edward Diener 30 Mar '04

30 Mar '04

I attempted to build bcp with Jam V2 and como under Win2k with the latest CVS source and the latest bjam.exe. My como installation is in H:\Utilities\Comeau directory and is already set up to use a back end compiler. I executed: bjam --v2 -sCOMO_PATH=H:\Utilities\Comeau -sTOOLS=como from the boost\tools\bcp directory and received this output indicating an error: "H:/Programming/Version Control/CVS/Home/boost/tools/build/v2/util\order.jam:38:in loaderror: no native rule "add-pair" defined in module "class@order." H:\Programming\Version Control\CVS\Home\boost\tools\build\v2/kernel\modules.jam:259: in import H:/Programming/Version Control/CVS/Home/boost/tools/build/v2/tools\unix.jam:16:in load H:\Programming\Version Control\CVS\Home\boost\tools\build\v2/kernel\modules.jam:259: in import H:/Programming/Version Control/CVS/Home/boost/tools/build/v2/build\toolset.jam:259: in toolset.inherit H:/Programming/Version Control/CVS/Home/boost/tools/build/v2/tools\gcc.jam:19: in load H:\Programming\Version Control\CVS\Home\boost\tools\build\v2/kernel\modules.jam:259: in import..\..\project-root.jam:2: in modules.load H:/Programming/Version Control/CVS/Home/boost/tools/build/v2/build\project-roots.jam:160: in object(project-root-object)(a)1.initialize H:/Programming/Version Control/CVS/Home/boost/tools/build/v2/build\project-roots.jam:52: in project-roots.load H:/Programming/Version Control/CVS/Home/boost/tools/build/v2/build\project.jam:61: in project.load H:/Programming/Version Control/CVS/Home/boost/tools/build/v2\build-system.jam:75: in load H:\Programming\Version Control\CVS\Home\boost\tools\build\v2/kernel\modules.jam:259: in import H:\Programming\Version Control\CVS\Home\boost\tools\build\v2/kernel/bootstrap.jam:120: in boost-build H:\Programming\Version Control\CVS\Home\boost\boost-build.jam:12: in module scope" What am I missing or what did I do wrong ? Finally it would be nice if Boost could distribute some batch files ( or Unix shells ) for each compiler toolset in which all the builder would have to do is to enter the mandatory information, as optional arguments since the environment variable might be already set, for that toolset in order to trigger off the build, rather than have to worry about command line arguments. I know the command line isn't complicated but anything to simplify the end user's or developer's burden in using Boost Build would get my vote. I have no doubt it is an excellent system, but it is a bear to learn, when all one wants is to simply build portions of Boost. I know this sounds lazy but then I am a very lazy programmer in all but programming and documentation where I am just mildly lazy <g> .

4 8

Re: [boost] Re: Standard C Library and C++ / BOOST
by Reece Dunn 30 Mar '04

30 Mar '04

Rob Stewart wrote: >From: "Reece Dunn" <msclrhd(a)hotmail.com> > > The errorcheck class now has a policy-based implementation, so it would >look > > something like: > > > > template< typename ErrorStorage, typename ErrorMsgStorage > > > class errorcheck: public Storage, public MsgStorage > > { > > private: > > inline errorcheck( const Storage & s, const MsgStorage & ms ): > > Storage( s ), MsgStorage( ms ) > > { > > } > > public: > > inline errorcheck( typename Storage::error_type e ): > > Storage( e ), MsgStorage() > > { > > if( failed()) > > throw( errorcheck< Storage, MsgStorage >( *this, *this >)); > > } > > }; > > > > which, IMHO, is more confusing than the straight throw( *this ), but >does > > not use the copy constructor, relying instead of the fully constructed > > Storage and MsgStorage base classes. > >I wouldn't call it confusing, though I'd expect that you'd need >to document why you couldn't do the more obvious thing. I mean confusing in that you have errorcheck( *this, *this ) so it is harder to see what is going on. I have added a comment line explaining why this is done and would also put this in the docs. >I do have to ask why the private ctor takes a MsgStorage object >to copy since the MsgStorage in this case will be the default >constructed base subobject created in the initializer list of the >throwing ctor. As written, the second argument to that ctor is >useless; the private ctor could default construct its MsgStorage >subobject. >Actually, though, I had this in mind: >template <typename ES, typename MS> >class error_check : public ES, public MS >{ > error_check(typename ES::error_type e, std::nothrow_t) > : ES(e) > { > } > >public: > error_check(typename ES::error_type e) > : ES(e) > { > if (failed()) > { > throw error_check<ES,MS>(e, nothrow); > } > } >}; What about when you use boost::policy::errormsg_storage instead of boost::policy::no_errormsg_storage? Doing this allows the following: typedef boost::errorcheck< boost::policy::error_storage<>, boost::policy::errormsg_storage > errorcheckmsg; try { errorcheckmsg em; em( "oops!" ) = -3; // note the special syntax } catch( errorcheckmsg em ) { std::cout << "error: " << em.get_msg() << '\n'; } resulting in "error: oops!" being outputted. Using your method, the message string will ont be passed and thus you would get "error: unspecified error"! That is why I implemented it as above. >(Note that you used "Storage" where you should have used >"ErrorStorage" in the excerpt above. I just used abbreviations.) That was my bad: ErrorStorage and Storage are the same. Regards, Reece _________________________________________________________________ Express yourself with cool emoticons - download MSN Messenger today! http://www.msn.co.uk/messenger

2 1

Re: [boost] Re: IndexedSet Review: unified proposal for naming
by JOAQUIN LOPEZ MU?Z 30 Mar '04

30 Mar '04

----- Mensaje original ----- De: Pavel Vozenilek <pavel_vozenilek(a)hotmail.com> Fecha: Martes, Marzo 30, 2004 7:54 pm Asunto: [boost] Re: IndexedSet Review: unified proposal for naming > > "Joaquín Mª López Muñoz" <joaquin(a)tid.es> wrote > > > * Proposal: boost::container::multi_index > > > So far no other library sits in boost::container. > Existing containers probably won't move there > the future (work, compatibility). > Well, I haven't any special desire to move into boost::container, but seems like there's a general consensus that such grand namespaces should begin to emerge. I just have no strong opinion on this, my proposal only meant to collect the feedback gotten from the reviewers. Either way, I think the proposed naming works even without ::container:: Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

Any way to speed my use of boost_pp macros?
by Larry Evans 30 Mar '04

30 Mar '04

The file, http://groups.yahoo.com/group/boost/files/managed_ptr/ctor_fwder.zip , shows a simple program using boost/preprocessor macros taking 17secs to execute. If anyone has some suggestions for speeding this up, I'd certainly appreciate it. TIA.

5 14

Re: [boost] Re: Standard C Library and C++ / BOOST
by Reece Dunn 30 Mar '04

30 Mar '04

>From: Rob Stewart <stewart(a)sig.com> >From: "Reece Dunn" <msclrhd(a)hotmail.com> > > So the errorcheck object will be in a half-constructed state. That is, >the > > int will be constructed, but the errorcheck object isn't, therefore the > > int's destructor will be called, but errorcheck's deconstructor will >not. > > > > The solution would therefore be to throw an intermediate object, like >the > > Trules from the C++ Templates book by David Vandervoorde and Nico >Josuttis. > > This would then get around the throwing in a constructor problem. >Why not throw a new errorcheck object using a private ctor that >stores but doesn't check the return value? That would work (I realised an implementation after the post). But this is what I was trying to achieve using the copy constructor (and copy assignment), since that copies the object, but does not throw on failure. The errorcheck class now has a policy-based implementation, so it would look something like: template< typename ErrorStorage, typename ErrorMsgStorage > class errorcheck: public Storage, public MsgStorage { private: inline errorcheck( const Storage & s, const MsgStorage & ms ): Storage( s ), MsgStorage( ms ) { } public: inline errorcheck( typename Storage::error_type e ): Storage( e ), MsgStorage() { if( failed()) throw( errorcheck< Storage, MsgStorage >( *this, *this )); } }; which, IMHO, is more confusing than the straight throw( *this ), but does not use the copy constructor, relying instead of the fully constructed Storage and MsgStorage base classes. Regards, Reece _________________________________________________________________ Find a cheaper internet access deal - choose one to suit you. http://www.msn.co.uk/internetaccess

2 1

RE: [boost] Region Library?
by Powell, Gary 30 Mar '04

30 Mar '04

2D games do this all the time. It's more than a OS problem. -Gary- -----Original Message----- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Allan Odgaard Sent: Tuesday, March 30, 2004 11:04 AM To: boost(a)lists.boost.org Subject: [boost] Region Library? A region is used as the term to describe a set of rectangles -- e.g. could be as simple as std::vector<rectangle>. When working with regions, one often needs to perform various operations like finding the intersection of two regions, the union, subtract one region from another or xor two regions (which is the union minus the intersection). I would like to know if there is a) any interest in such a library and/or b) if such a library already exists? I figure the usefulness of such a library mostly has to do with optimizing (and clipping) refresh in a graphical view port, which is often something the operating system takes care of. And thus user code rarely has to deal with these things. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

RE: [boost] RE: Re: Standard C Library and C++ / BOOST
by Reece Dunn 30 Mar '04

30 Mar '04

Vladimir Prus wrote: >Reece Dunn wrote: > > >>Yes, you're right. However, there's one additional wish -- I'd like an > >>appraoch different macroses for different functions. E.g. for POSIX >calls > >>I only encounter -1 returns and NULL returns for error reporting. So I'd > >>like > > > >> int tty = check(open(check(ctermid(0)), O_RDRW); > > > >>to work. I guess this could be done by providing two overloads for the > >>'Wrong' function...., but not, the 'Enforcer' template only works for > >>specific type of return value :-( > > > > My errorcheck class (see other posts) has an error policy where you can > > change the fail test. The default is to test errorcode < 0. > >The code you've posted had the check hardcoded, maybe I've missed some >other >post? The error_storage::failed() function has the hard-coded check, but the errorcheck class gets the storage (and check) policy as a template, so you can provide your own class to perform a custom check. > > A current weakness is that it does not return the value passed to it on > > assignment, so you cannot use exactly like the above example. I have >been > > updating it to support errno handling, but this (at present) requires > > something like: > > > > boost::errorcheck< ... > check; > > > > FILE * fp = ::fopen( 0, "r" ); > > check( fp != 0 ); // assert-like syntax > > ::fclose( fp ); > > > > If you are interested, I'll work on supporting constructs like your > > example above. > >I actually wonder if we need a class. Does it have any advantages over >function? E.g: > template<class Checked = default_checker, class T = void> > T check(T t) > { > if (Checker(t)) > throw ... > return t; > } I suppose it comes down to what you are used to and aesthetics. I have been using MS COM objects heavily that rely on HRESULT error code returns, where the code looks like: HRESULT hr; IHTMLStyle * s = 0; if( FAILED( hr = elem -> get_style( &s ))) goto clean; // use the style object clean: if( elem != 0 ) elem -> Release(); if( s != 0 ) s -> Release(); Which is ugly IMHO, so I use a smart pointer for COM object management and have a com::hresult class for storing the HRESULT, mapping it to a string, etc. The errorcheck class is based on a com::result (throwing version of com::hresult) now defined using errorcheck: typedef boost::errorcheck< hresult > result; I suppose there are applications for both approaches, depending on what style you want, what facilities you want, etc. Regards, Reece _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger

1 0

RE: [boost] Standard C Library and C++ / BOOST
by Klaus Nowikow 30 Mar '04

30 Mar '04

Reece Dunn wrote: [snip] > A trick I use when handling HRESULT error codes is to have a > class like this > (adapted for int error type): > > class errorcheck > { [snip] > public: > inline errorcheck( int ec ): error( ec ) > { > if( ec < 0 ) throw( *this ); > } Careful. Throwing an exception from a constructor means that the object won't be constructed (i. e., does not exist). So you are throwing a non-existing object here. Or am I wrong? Best regards, Klaus

5 8

RE: [boost] Re: Standard C Library and C++ / BOOST
by Klaus Nowikow 30 Mar '04

30 Mar '04

> From: Rene Rivera [mailto:grafik.list@redshift-software.com] > Rob Stewart wrote: > > From: Rene Rivera <grafik.list(a)redshift-software.com> > > > >>Gennaro Prota wrote: > >> > >>>On Sat, 27 Mar 2004 19:23:50 -0500, David Abrahams > >>><dave(a)boost-consulting.com> wrote: > >>> > >>>>"Klaus Nowikow" <nowikow(a)decomsys.com> writes: > >>>> > >>>>>Reece Dunn wrote: > >>>>>[snip] > >>>>> > >>>>> > >>>>>> class errorcheck > >>>>>> { > >>>>> > >>>>>[snip] > >>>>> > >>>>>> public: > >>>>>> inline errorcheck( int ec ): error( ec ) > >>>>>> { > >>>>>> if( ec < 0 ) throw( *this ); > >>>>>> } > >>>>> > >>>>>Careful. Throwing an exception from a constructor > >>>>>means that the object won't be constructed (i. e., does > not exist). > >>>>>So you are throwing a non-existing object here. > >>>>> > >>>>>Or am I wrong? > >>>> > >>>>You're wrong. *this is copied before it is thrown. > Still, the idiom > >>>>above seems a bit suspicious, unless you somehow prevent > derivation > >>> > >>>>from errorcheck. > >>> > >>>I can't believe you are justifying the above. You copy an > object that > >>>doesn't exist yet! (The class is not a POD and has a non trivial > >>>constructor - and even if this wasn't the case...) > >> > >>I don't see how the object is not fully initialized inside > its constructor?? > >>Could you explain your objection? > > > > > > Until the ctor finishes -- after the closing } -- there is no > > object (see 3.8/1). > > Yes the object lifetime hasn't started... but the object is > initialized. Which > according to 12.7 allows for referring to members of the > object directly or > indirectly, in this case by a copy ctor function. I think you are right. When I posted the message above, I didn't take into consideration that the object (*this) is copied before it is thrown. Best regards, Klaus

1 0