Re^2: How can i prevent perltidy from adding a semicolon after an ellipsis?

Ah, i see:

karls-mac-mini:monks karl$ perl -E 'sub foo{...}; foo();'
Unimplemented at -e line 1.
karls-mac-mini:monks karl$ perl -E 'sub bar{...;}; bar();'
Unimplemented at -e line 1
[download]

Both are valid. I didn't know this.

I didn't run perl -c on the concerning file and thought things went wrong.

On the other hand: I don't want perltidy to change my valid code. Nitpicking, sure.

Thanks and best regards, Karl

ŤThe Crux of the Biscuit is the Apostropheť

perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'Help

Comment on Re^2: How can i prevent perltidy from adding a semicolon after an ellipsis? Select or Download Code

Replies are listed 'Best First'.
Re^3: How can i prevent perltidy from adding a semicolon after an ellipsis? by LanX (Saint) on Nov 18, 2017 at 19:46 UTC
From the docs You can only use the elliptical statement to stand in for a complete* statement.* So the semicolon is needed, if the "yadda yadda" is followed by other statements. And a trailing semicolon in a functions body is certainly not bad style. Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :) Je suis Charlie!}	[reply]
Re^4: How can i prevent perltidy from adding a semicolon after an ellipsis? by karlgoethebier (Abbot) on Nov 18, 2017 at 19:48 UTC
Thanks Rolf. ŤThe Crux of the Biscuit is the Apostropheť `perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'`Help	[reply] [d/l]