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: | Bryan Ewbank <ewbank@lucent.com> |
Newsgroups: | comp.compilers |
Date: | 23 Nov 1999 00:36:47 -0500 |
Organization: | Lucent Technologies |
References: | 99-11-117 99-11-128 |
Keywords: | yacc, errors |
> Objective is to cleanup memory allocations on parse errors.
Since there are parse errors, isn't the program going to exit? If so,
why bother cleaning up?
Note that this does not work for destructors of created objects, since
there can be all kinds of side effects :-)
--
Bryan Ewbank <><
Lucent Technologies
http://www.lucent.com, mailto:ewbank@lucent.com, 630.979.1871
[Lots of programs call yyparse() more than once, to parse line by line
and the like. -John]
Return to the
comp.compilers page.
Search the
comp.compilers archives again.