Re: and multiple statements

print "this is bad", next;
[download]

means

print("this is bad", next);
[download]

Disambiguate with parens

($istrue) or print("this is bad"), next;
($istrue) or (print "this is bad"), next;
[download]

Or use do as previously shown

($istrue) or do { print "this is bad"; next; };
[download]

But an if would be clearer.

if (!$istrue) { print "this is bad"; next; }
[download]

Update: Added missing "!" as per reply.

Comment on Re: and multiple statements Select or Download Code

Replies are listed 'Best First'.
Re^2: and multiple statements by cmac (Monk) on Jun 06, 2010 at 08:37 UTC
`if (!$istrue) { print "this is bad"; next }`	[reply] [d/l]
Re^2: and multiple statements by JavaFan (Canon) on Jun 06, 2010 at 11:46 UTC
But an if would be clearer. Is it? Always? For everyone? Considering the idom `open ... or die ...` is quite common, I'd say that `open ... or do {...;...}` [download] is clearer than `if (!open ...) { ...; ... }` [download] I'd certainly write the former.	[reply] [d/l] [select]
Re^3: and multiple statements by ikegami (Patriarch) on Jun 06, 2010 at 19:22 UTC
It's quite common because it's required in the case of `open(my $fh, ...)`, not because it's clearer.	[reply] [d/l]
Re^4: and multiple statements by JavaFan (Canon) on Jun 06, 2010 at 21:12 UTC
Required? I don't follow. `if (!open my $fh, "<", "filename") { warn "Whatever"; return; }` [download] is perfectly valid code. There's no requirement that that is to be written as `open my $fh, "<", "filename" or do {warn "Whatever"; return;};` [download]	[reply] [d/l] [select]
Re^5: and multiple statements by ikegami (Patriarch) on Jun 06, 2010 at 23:03 UTC