$include_dir="/home/hyper-archives/boost-build/include"; include("$include_dir/msg-header.inc") ?>
From: David Abrahams (gclbb-jamboost_at_[hidden])
Date: 2003-05-10 12:09:33
Ali Azarbayejani <ali_at_[hidden]> writes:
> Each class declaration requires a "rule" declaration followed by a
> "class" declaration, making it difficult to see at a glance whether
> a rule is a regular rule or a class definition. Short of a core jam
> modification to allow a more obvious declaration, it may be possible
> to reduce confusion by allowing the placing of the "class"
> declaration just before the "rule" declaration. David plans to
> explore this possibility. We're not sure there is an easy solution.
An even easier solution:
rule foo.__init__ ( args * )
{
base.__init__ ( ... ) ;
rule method ( arg ) { }
}
class foo : base1 base2 ;
We can see that foo is a class by convention: its __init__ function
is declared.
Requires no core changes at all and just a minor tweak to class.jam.
-- Dave Abrahams Boost Consulting www.boost-consulting.com