> > And from a syntax perspective, it's a bad idea. x[] is much > > more often a typo than an intentional attempt to index a > > zero-dimensional array. > > but how often is it a typo? > > for example, judging from c.l.python traffic, forgetting to add a return > statement is a quite common, but I haven't seen anyone arguing that we > deprecate the implied "return None" behaviour.
Sounds like a terrific idea. The implicit None behaviour has hit me many times and: something = somefunc() is almost always an error if somefunc() doesn't have an explicit return statement. I don't know how difficult it is to get rid of the implicit "return None" or even if it is doable, but if it is, it should, IMHO, be done. -- mvh Björn _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
