I more or less endorse the "lint" idea in the sense of saying we can do
better than YACC at identifying the cause of some errors. If such a tool
were created, when the YACC error reporter kicks in, we could trigger it
from the compiler as an "autolint" feature that would look back earlier in
the code to see if there is something else wrong that technically YACC
couldn't identify as a syntax error.
Clint
On Wed, Jan 26, 2011 at 1:22 PM, John Sampson <[email protected]> wrote:
> I had a syntax error message about a semi-colon. I tracked the cause
> down to not following the word "while" with the word "do" - a long way from
> the line the error message was telling me was wrong. Don't ask me what this
> has to do with a semi-colon.
>
> There might be scope for a 'lint' type program that concentrates on
> giving helpful information about errors without the added burden of trying
> to compile the code. As it is, perhaps the best error message is "There is
> an error in this code". This would not be misleading.
>
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Unicon-group mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unicon-group
