Re: Semicolon terminating paren-less call to 'opendir' triggers a bogus warning

in reply to Semicolon terminating paren-less call to 'opendir' triggers a bogus warning

The warning isn't bogus, because you could have meant my ($h, $s)

But it's only warning, which is not really relevant for golfing and disabled easily.

Cheers Rolf
_{(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)

Wikisyntax for the Monastery}

Comment on Re: Semicolon terminating paren-less call to 'opendir' triggers a bogus warning Download Code

Replies are listed 'Best First'.
Re^2: Semicolon terminating paren-less call to 'opendir' triggers a bogus warning by BillKSmith (Monsignor) on Sep 08, 2023 at 02:04 UTC
Why doesn't the first example give the same warning? The only difference that I see is the semicolon. Bill	[reply]
Re^3: Semicolon terminating paren-less call to 'opendir' triggers a bogus warning by LanX (Saint) on Sep 08, 2023 at 07:12 UTC
You are right, it's only the semicolon. The parser is full of heuristics trying to DWIM ambiguities. So probably that's one of the side effects, when the code ends abruptly. 🤷‍♂️ Cheers Rolf _{(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :) Wikisyntax for the Monastery}	[reply]

In Section Seekers of Perl Wisdom