The numbers in parentheses after syntax error messages are the YACC parse
state and the current input token. There is an incomplete mapping from these
integer pairs into meaningful syntax error messages, and you get the numbers
in parentheses when the mapping does not have a message for that parse
state.
The current, incomplete mapping needs to be finished. It starts with all the
parse states for which Icon knew how to produce a diagnostic message, and
adds various ones for Unicon constructs, but really we need a way to
generate examples for ALL the parse states.
Completing the mapping will happen when a volunteer does it, or when a
paying customer demands it, or when my priority queue lets it slip in.
Cheers,
Clint
On Wed, Jan 26, 2011 at 12:53 PM, John Sampson <[email protected]> wrote:
> Hello -
>
> Can the numbers in parens after syntax error messages be used to give
> any clue what they mean?
>
> Regards
>
> _John Sampson_
>
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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
