From: Eric B. R. <eb...@tc...> - 2003-03-25 15:22:14
|
On Tuesday, March 25, 2003, at 02:57 AM, Endre St=F8lsvik wrote: > | Brian convinced me that we can somewhat easily get this particular > | error message changed to something like: > | "no zero-arg macro named #contentString" > > That would of course be _heaps and bounds_ (is that the English term?) "Leaps and Bounds", but I kinda like "Heaps and Bounds"! > better, and would of course lead me to look for the bug in the=20 > args-list, > not scrutinize the spelling.. > > And it's a much better error message anyway, since it says "I _do_=20 > have a > directive of that name, but the one I know of have got some arguments, > 'kay?". > > But .. shouldn't all such error messages say "directive or macro" .. ? In this case, we'd be able to guess that it was a #macro. > | However, we're still not gunna be able to pick up on the fact that=20= > the > | right-hand paren is missing. That's something you'll still need to > | figure out manually by looking at the error message and line/column > | information. > > The parser often says things like "Found this thing, was expecting one=20= > of > these thingys ' ... ' ". Why couldn't it notice that there is missing = a > paren, given that it encounters "}" before the started "(" ? No, because the parser doesn't count parens or braces. At least I=20 think that's the case. eric= |