🚀 go-pugleaf

In article <4kqe6q$1tm@innocence.interface-business.de>,
J Wunsch <joerg_wunsch@uriah.heep.sax.de> wrote:
>stok@kalypso.cybercom.net (Michael J. Stok) writes:
>
>> The {}s shouldn't be optional!  That's the route Perl took with blocks 
>> after for, if, while, else etc.  Just because C and similar languages 
>> have the "optimisation" that they the {}s are optional doesn't mean it's 
>> right :-)
>
>Just because Perl allows for the "optimisation" to put the "if" before
>or after the statement, and mandates the curlies _for one of the options_,
>doesn't make the code better per se. :-)

Perl cops out of resolving the classic ``if/then ambiguity'' by forcing the
required syntactic units to be compound statements, doesn't it?

In Perl, you write:

	if (....) 
		if (....)
			if (....)
				statement;
	else
		statement;

The programmer is forced to ``disambiguate'':

	if (....) {
		if (....) {	
			if (....) {
				statement;
			}
		}
	} else {
		statement;
	}

What a PITA. (And I ain't referring to an Italian meal also known as a pizza
pocket, either).