From: Andrew Svetlov Date: Wed, 5 Dec 2012 15:59:10 +0000 (+0200) Subject: Update comment: SAVE_EXC_STATE and SWAP_EXC_STATE macroses are saave_exc_state and... X-Git-Tag: v3.3.1rc1~560 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c37cfd67097f78617213693a3be918aaf10cc3d6;p=python Update comment: SAVE_EXC_STATE and SWAP_EXC_STATE macroses are saave_exc_state and swap_exc_state functions now. --- diff --git a/Include/frameobject.h b/Include/frameobject.h index ac2f790d13..33f73af52a 100644 --- a/Include/frameobject.h +++ b/Include/frameobject.h @@ -33,8 +33,8 @@ typedef struct _frame { frame (which shouldn't be impacted when the generator "yields" from an except handler). These three fields exist exactly for that, and are unused for - non-generator frames. See the SAVE_EXC_STATE and SWAP_EXC_STATE - macros in ceval.c for details of their use. */ + non-generator frames. See the save_exc_state and swap_exc_state + functions in ceval.c for details of their use. */ PyObject *f_exc_type, *f_exc_value, *f_exc_traceback; PyThreadState *f_tstate;