another near-sighted, time-wasting syntax enhancement idea
Carl Banks
idot at vt.edu
Sat Jun 8 21:35:57 EDT 2002
Chris Liechti <cliechti at gmx.net> wrote in message news:<Xns92265AD72BE0cliechtigmxnet at 62.2.16.82>...
> idot at vt.edu (Carl Banks) wrote in
> news:e395b886.0206051956.5f447e9b at posting.google.com:
> > class BigLongClassThatRunsUntilEOF::
> >
> > def __init__ (self):
> > pass
> >
> > def whatever (self):
> > pass
> >
> > ...
> >
> > Two colons after the class (or whatever) definition means the block
> > continues until EOF and is not indented. Good for big, long classes
> > that take up a whole module. Been suggested before, I'm sure.
>
> i don't see any advantages for that. it's a very suptile difference almost
> not viewable those "::", it makes code bad readable.
class NewsConverse:
def write_reply (self, message):
if self.poster_misses_point (message):
self.set_paragraph_reply("Code scrunched up "
"against the right "
"margin can be pretty "
"unreadable itself.")
> doesn't your editor has auto indentation? don't use notepad an switch to a
> real editor <wink>.
I'm pretty sure if it's a feature, emacs has it. <wink>.
--
CARL BANKS
More information about the Python-list
mailing list