Re^3: What esteemed monks think about changes necessary/desirable in Perl 7 outside of OO staff

I never had problems with omitting semicolons; maybe it's because of the extensive Pascal training.

If you write short subroutines, as you should, you don't suffer from misplaced closing curly braces. I had problems with them, especially when doing large edits on code not written by me, but the editor always saved me.

Both puns intended.

map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

Comment on Re^3: What esteemed monks think about changes necessary/desirable in Perl 7 outside of OO staff Download Code

Replies are listed 'Best First'.
Re^4: What esteemed monks think about changes necessary/desirable in Perl 7 outside of OO staff by Fletch (Bishop) on Sep 10, 2020 at 19:27 UTC
More or less agree WRT mismatched closing curlies. I see it pretty much entirely as an editor issue. (I mean isn't that the whole python argument for Semantic-Whitespace-As-Grouping? At least I recall that ("Your editor will keep it straight") being seriously offered as a valid dismissal of the criticism against S-W-A-G . . .) The cake is a lie. The cake is a lie. The cake is a lie.	[reply]
Re^5: What esteemed monks think about changes necessary/desirable in Perl 7 outside of OO staff by likbez (Sexton) on Sep 10, 2020 at 21:37 UTC
I mean isn't that the whole python argument for Semantic-Whitespace-As-Grouping? No the argument is different, but using indentation to determine block nesting does allow multiple closure of blocks, as a side effect. Python invented mixed solution when there is an opening bracket (usually ":") and there is no closing bracket -- instead the change in indent is used as the proxy for the presence the closing bracket. The problem is that it breaks too many other things, so here the question "whether it worth it" would be more appropriate, then in the case of soft semicolons or "reverse labels on "}" like "}LABEL" .	[reply]