Message140506
| Author |
pitrou |
| Recipients |
Arfrever, Trundle, benjamin.peterson, eric.snow, georg.brandl, loewis, marienz, ncoghlan, pitrou, terry.reedy |
| Date |
2011年07月16日.22:28:55 |
| SpamBayes Score |
2.2723125e-05 |
| Marked as misclassified |
No |
| Message-id |
<1310855265.3630.10.camel@localhost.localdomain> |
| In-reply-to |
<CAPZV6o9hB_R4OR2EL9kpMmtnQr_q2TsUs5zA-tR6sAtfUtJBYA@mail.gmail.com> |
| Content |
> I content that in normal code, it is so extremely rare as to be
> unheard of, to get exceptions about the parser stack overflowing or
> segfault the compiler by too deep nesting. People who are doing this
> (generally to prove the point about limitations of the compiler) are
> smart enough to know exactly what "parser stack overflowed" means and
> separate that from Python as the language. Adding a new exception is
> solving a non-existent problem.
Agreed with Benjamin. Also, "why something is wrong" can simply be told
in the exception message. |
|