From: Alan Gutierrez (alan-jamboost_at_[hidden])
Date: 2005-01-02 09:33:23
* David Abrahams <dave_at_[hidden]> [2004-12-29 11:31]:
> Alan Gutierrez wrote:
> > I found it illuminating to read through the code in the kernel
> > directory.
> > Boost.Build v2 employs an implementation of polymorphic classes
> > that were built on top of the Jam syntax. It was really hard to
> > figure out what is going since a lot of the constructs are not
> > pure Jam, and not a description of a build process as one might
> > expect.
> > For some reason, finding the lines between Jam, Boost.Build, and
> > the toolsets makes me less anxious.
> I really hope that kind of low-level detail isn't neccessary for
> everyone. If it is, we really need to fix the documentation (well, I
> already know we need to fix the documentation).
I don't think the distinctions between the language, the
library, and the application are low-level detail.
When I first read the documentation, I came to a point where I
was told that a more complex generator required you to create
your own class.
And I'm like, class? That's the first time you told me that Jam
was object based. Then I'm looking at Perforce/Jam. Okay,
where's the part about creating my own class. How do I reference
this/self? How do I override methods? Is there a common object root?
I came to the point in the documentation, that said I might have
to write classes, which blew my concept of the scope of what I
was learning, which shakes confidence in how long and how
difficult it will be to learn.
I need to start out with an archectural overview, so I can
devise my personal lesson plan.
-- Alan Gutierrez - alan_at_[hidden]
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk