GW$BA0$KAj
$B%\%?%s$R$H$D$GL5NA$G(B1$B1_J,$bM7$Y$^$9!#(B 1$B1_J,$"$l$PNA6b$,[EMAIL PROTECTED]($^$9!#(B $B:#$9$0$K$G$b;n$7$F$_$F2<$5$$!#(B http://awg.webchu.com/?springe ___ Help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
Re: %destructor and stack overflow
On 2005-04-27, at 23:19:43 +0200, Hans Aberg wrote: > At 21:20 +0200 2005/04/27, Marcus Holland-Moritz wrote: > >%destructor looks like it has the ability to be this "something > >better", but IMO it currently isn't as good as it could be (i.e. > >it is worse than my solution with regard to potential memory > >leaks arising from parser stack overflow). > > The intent of %destructor is to help cleanup during error stack > unwinding. If one can somehow make a stack overflow cause an error, > which in its turns causes the stack to unwind, then the cleanup would > take place via %destructor. > > >I think #define'ing YYMAXDEPTH to MAXINT (or any other XXL number) > >isn't a good idea. I know that no sane code requires the parser > >stack to be as large as 1000 items. So with YYMAXDEPTH = 1 > >I'm clearly on the safe side. And I prefer to have an error at a > >well-defined boundary rather than some part of the application > >running out of "real" memory when passed illegal input. > > So if you get a stack overflow error, what do you want to happen? > Clearly, the parser must be taken down. You want it then to done so > that stack cleanup takes place. Right? Possibly, the same cleanup > actions as those in %destructor should be used. Yes, that's exactly what I'm talking about. When the parser detects a stack overflow, it should call the cleanup actions defined via %destructor for all symbols on the stack (and the symbol causing the overflow) before it returns. Marcus ___ Help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
Re: %destructor and stack overflow
At 22:47 +0200 2005/04/28, Marcus Holland-Moritz wrote: > So if you get a stack overflow error, what do you want to happen? Clearly, the parser must be taken down. You want it then to done so that stack cleanup takes place. Right? Possibly, the same cleanup actions as those in %destructor should be used. Yes, that's exactly what I'm talking about. When the parser detects a stack overflow, it should call the cleanup actions defined via %destructor for all symbols on the stack (and the symbol causing the overflow) before it returns. So then we know what you want to have. Here, I must ask Paul or Akim (who wrote the %destructor feature) help me out. -- Hans Aberg ___ Help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
Re: %destructor and stack overflow
Marcus Holland-Moritz <[EMAIL PROTECTED]> writes: > When the parser detects a stack overflow, it should call > the cleanup actions defined via %destructor for all symbols > on the stack (and the symbol causing the overflow) before > it returns. Yes, that sounds right. Can you write and test a patch to data/yacc.c that does that? Presumably it would be some code executed just after the "parser stack overflow" message, that would call yydestruct. ___ Help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
Cost Accounting Software Developer Needs Sales Reps
We are a sales & marketing consulting firm that represents a manufacturer of job cost accounting & management software. Our client asked us to contact your company to see if you would be interested in becoming an independent sales rep for them in your area. Our client is a leading provider of fully integrated job-cost accounting and management software solutions for the mid-market construction industry. If you are interested in becoming an independent sales rep for our client, please return by email your mailing address and phone / fax number. We will immediately mail you a brochure on our client for your review. There are no obligations, products or services to buy if you wish to respond. Our client wishes to pay you for your services. Pat BartleyPresident - CEOOuterSales11693 San Vicente Blvd., Suite 316Los Angeles, CA 90049 Phone: 818-342-4576Fax: 818-342-3748 Email: [EMAIL PROTECTED] Note: We must give you a "Notice of Opt-Out Opportunity" which requires us to provide a cost-free mechanism to stop any future emails. If you wish not to receive any future emails from us, the following Opt-Out options are available to you: (1) You can send email to the following email address: [EMAIL PROTECTED] (2) You can send mail to the following postal address: OuterSales,11693 San Vicente Blvd., Suite 316, Los Angeles, CA 90049(3) You can call the following toll free telephone number: 800-929-2157 (4) You can fax the following fax number: 818-342-3748. Thank you for your understanding and cooperation. ___ Help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
