🚀 go-pugleaf

Kazimir Kylheku <c2a192@ugrad.cs.ubc.ca> wrote:
	>snip<
: Actually I do program much. I wouldn't talk if I were you, read on...
	Hmm, didn't see my simily did you?  Oh well...
	>snip<
: In your if statement, the else clause gets executed if *any one* of the
: test expressions fails! ``if (1 && 1 && 0)'' will launch into the *else* clause.
: In MY if statement, the else clause only gets executed it the *outermost* test
: condition fails. ``if (1) if (1) if (0) statement 1; else statement2;'' will
: cause *neither* statement1 *nor* statement2 to be executed!
	There are ways around this as well, however simply taking the 10
	secs of time to add the }{s as your past example did would be the
	easyest way in Perl.

: See, the two are not equivalent at all!
	You're right, and that teaches me to followup after a double
	espresso. ;-}

: ... and I still think Perl's handling of the classic if/then ambiguity during
: LR parsing is a lame copout. But I like it very much otherwise...
	... and I still wonder how you can call good programing habbits a
	"lame copout". But I like your ideas vary much otherwise...

	Just to note, the optional omission of }{s around loops in C is by
	far one of it's sillyest "features", IMHO, and should never have
	been allowed into the language.  But I digress... :)
______
     /  Spelling mistakes?  Their couldn't be. -My modem is error correcting.
    /
   /    Zenin@Best.com                   ---->>ROCKY HORROR ARCHIVE<<----
  /      ___    __  o   __
 /      /___\ |/  \ | |/  \                 http://www.best.com/~zenin/
/_______\___  |   | | |   |_______________________________________________