News for hackers. Stuff that matters.
Re:C-style vs. Python-style syntax: which one would you pref... by llimllib on Sunday December 14, 2008 @01:10PM (#397501)
Python already has an optional end:

    def something:
        alpha()
        omega()
    #end
I think introducing it as a special case, with no semantic value, into your parser would be an extremely poor idea.
Re:C-style vs. Python-style syntax: which one would you pref... by mojuba on Sunday December 14, 2008 @02:00PM (#397540)
True, except #end doesn't verify you are at the correct level of indentation. This, instead, would be more appropriate:

  def something:
    ...
  end def
but then it makes indentations insignificant altogether.
Re:C-style vs. Python-style syntax: which one would you pref... by llimllib on Sunday December 14, 2008 @02:11PM (#397558)
That would indeed make it semantically valuable. I assume you'd have "end while", "end if", etc?

I can't say I'm a fan, but at least you'd be making it mean something if you did that.

(Also: why make it optional at that point? Seems like it should be required for simplicity's sake)

Re:C-style vs. Python-style syntax: which one would you pref... by mojuba on Sunday December 14, 2008 @02:44PM (#397581)
Shell/Ruby style (if ... endif) is not even considered because I'm no fan of it either. I think it already lost the battle to both C and Python styles.

It would be nice, however, to have some optional verification mechanism that allowed you to stay minimalist for as long as you wish, and to use closing tags for verification and/or aesthetical reasons - for example, when closing a superlong block.

Re:C-style vs. Python-style syntax: which one would you pref... by newt0311 on Tuesday December 16, 2008 @11:24AM (#399608)
Woah... Be wary of that attitude for there lies the path to C++ hell. Like people say, the path to hell is paved with good intentions.