This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ag6502
Recipients Mark.Shannon, ag6502, amaury.forgeotdarc, benjamin.peterson, francismb, ggenellina, pitrou, serhiy.storchaka, terry.reedy
Date 2012-08-20.06:53:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345445662.93.0.239125199081.issue5765@psf.upfronthosting.co.za>
In-reply-to
Content
I missed all the macrology present :-( ... the following is a patch that takes it into account (also defines a VISIT_QUIT macro to make more visible the exit points). The handling has been also extended to visit_stmt because the macros are shared.

Of course all this makes sense assuming that a cleanup in case of error is indeed desired...

BTW: shouldn't be all those statement macros of the "do{...}while(0)" form instead of just being wrapped in "{}" ? I see potential problems with if/else...
History
Date User Action Args
2012-08-20 06:54:23ag6502setrecipients: + ag6502, terry.reedy, amaury.forgeotdarc, ggenellina, pitrou, benjamin.peterson, Mark.Shannon, francismb, serhiy.storchaka
2012-08-20 06:54:22ag6502setmessageid: <1345445662.93.0.239125199081.issue5765@psf.upfronthosting.co.za>
2012-08-20 06:54:01ag6502linkissue5765 messages
2012-08-20 06:54:01ag6502create