|
Boost : |
From: scott (scottw_at_[hidden])
Date: 2004-02-08 18:37:16
> -----Original Message-----
> From: boost-bounces_at_[hidden]
> [mailto:boost-bounces_at_[hidden]]On Behalf Of David Abrahams
> Sent: Monday, February 09, 2004 9:28 AM
> To: boost_at_[hidden]
> Subject: [boost] Re: future of boost.threads
>
>
> "Jeff Garland" <jeff_at_[hidden]> writes:
>
> > On Sun, 08 Feb 2004 11:23:37 -0500, David Abrahams wrote
> >> Christopher Currie <christopher_at_[hidden]> writes:
> >>
<snip>
> >
> > Why?
>
> Because we don't have the luxury of an extra compilation stage like
> Corba does. There's no way to stop unwinding with catch(...), store
> whatever arbitrary exception object was thrown, and then
> rethrow it later.
I'm guessing this is a reference to IDL compilation?
I see that generally Boost does not make use of code generators (i.e.
something that fits into a build procedure like "yacc"). It does
(brilliantly)
use "code generation" from MPL lists but that's something else. I'm
sure everyone understands this already but just had to show that
I did also :-)
Out of curiosity; is this a Boost policy? I vaguely thought I had
read some Boost library requirements along these lines but now cant
find them.
Help?
<snip>
>
> --
> Dave Abrahams
> Boost Consulting
> www.boost-consulting.com
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
Cheers,
Scott
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk