| Related articles |
|---|
| Re: YACC error handling heirich@cs.ucsd.edu (1989-07-29) |
| yacc error handling ajayk@microsoft.com (Ajay Kalhan) (1999-11-19) |
| Re: yacc error handling ajayk@microsoft.com (Ajay Kalhan) (1999-11-21) |
| Re: yacc error handling ewbank@lucent.com (Bryan Ewbank) (1999-11-23) |
| Re: yacc error handling zalman@netcom11.netcom.com (Zalman Stern) (1999-11-28) |
| Re: yacc error handling mschweis@u.arizona.edu (Michael C Schweisguth) (1999-12-07) |
| Re: yacc error handling wfahle@bigfoot.com (Bill Fahle) (1999-12-24) |
| From: | "Ajay Kalhan" <ajayk@microsoft.com> |
| Newsgroups: | comp.compilers |
| Date: | 19 Nov 1999 22:39:51 -0500 |
| Organization: | Microsoft Corp. |
| Keywords: | yacc, errors, comment |
Objective is to cleanup memory allocations on parse errors. One
solution - Supplement rules with error rules in whose actions one can
do cleanup. Another solution - thread all allocated memory off a
global structure that can be destroyed at end of parsing.
Does anybody have any refinements or alternate suggestions?
Thanks.
Ajay
[I thread the allocated memory, it's more robust since it doesn't depend
on writing perfectly correct error rules. -John]
Return to the
comp.compilers page.
Search the
comp.compilers archives again.