From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-04-12 03:38:02
On Monday 10 April 2006 10:41, Vladimir Prus wrote:
> On Friday 07 April 2006 20:00, Rene Rivera wrote:
> > > This change cause stacktrace to be shown when Jamroot can't be found.
> > > Is this a desired behaviour?
> > >
> > > Users seems to be confused by long stacktrace, and in this case, it's
> > > not an internal error where stack trace makes sense.
> > >
> > > What do you think?
> > I agree... But we should have an equivalent to the "error" rule that
> > does it. It's was the raw ECHO+EXIT I wanted to remove, since the output
> > formatting wasn't consistent with the rest of the program error messages.
> Can you clarify? I though that added "error: " is the only convention for
> error messages we have at the moment.
Rene, any word from you on this? Basically, this issue breaks the
project_test3.py test, and I don't want to release M11 with braking
I can tweak the code mysef, but would rather know what was the issue with
original code, so that I don't reintroduce that issue again.
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
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