Thomas Wouters schrieb: > > > On 3/15/07, *Raymond Hettinger* <[EMAIL PROTECTED] <mailto:[EMAIL > PROTECTED]>> > wrote: > > My worry focuses on new-timers and SyntaxErrors. The worst part of > the new user experience is encountering a SyntaxError. > > > Please. I already said it would be a SyntaxError *with explanation*. > It's pretty easy to make a syntax error that goes "Did you mean 0t6065 > or 6065?". This would not be a syntax error handled by the parser, the > tokenizer really doesn't care about leading 0's and ast.c's parsenumber > (which would be the spot to raise it) has all the necessary information.
Until now, I skipped the octal thread. Now I read this and wondered, "what the hell is 0t6065 supposed to mean" and only from the context I gathered that it would be an octal literal... Seriously, nobody, even coming from another language, will be able to look at it and say, "yes, that's an octal literal." Georg _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
