merging from new parser branch (was Re: Common V3 coding bug)

[Phil Edwards <pedwards at disaster dot jaj dot com>]

I'm running the testsuite after merging -- can't see where adding
'template<>' and the like could break the current parser, but hey --
and will post a patch for approval before checking in (this first time,
at least; future merges should be even more trivial).

Other branches have added tags like 'new_wonkulator_mergepoint_20001234',
presumably to make future merging easier.  Do we need to do that?
I wouldn't think so, if the trunk is canonical for v3, but I'll abide by
y'all's decision.

Also:

> > > There might be bits
> > > that you would rather I'd do differently; for example, I've used `using 
> > > base::member;' rather than `this->member' in some of the changes thus
> > > far.

No you haven't.  :-)  Or rather, the only diffs showing up in my merge are
things like adding 'template<>' to specializations, and 'typename' at the
appropriate points.  I haven't seen any 'this->member' nor 'base::member'
showing up.  Have such changes already been checked into the trunk?


Phil

-- 
Would I had phrases that are not known, utterances that are strange, in
new language that has not been used, free from repetition, not an utterance
which has grown stale, which men of old have spoken.
                                     - anonymous Egyptian scribe, c.1700 BC