Re^2: strange arithmetic

Thanks for the clarification, but the above postings were indeed clear enough.

Had I simply used warnings (as suggested) I would not have come here - oh well...

With regard to "print" I always thought that if you use parenthesis around the arguments you should not have blanks between "print" and the opening parenthesis.
So in my ideal world Perl would distinguish between print($whatever) and print ($whatever), treating the parenthesis in the first case as part of the print-call while in the second case as part of the expression to be printed.

But that of course is only my taste and might open another can of worms...

Comment on Re^2: strange arithmetic Select or Download Code

Replies are listed 'Best First'.
Re^3: strange arithmetic by RonW (Parson) on Jan 09, 2015 at 22:44 UTC
In Perl, functions, including built in functions like print, act like named list operators. So Perl will look for a list of terms and expressions following the name of the function. Because, Perl, `(` and `)` are used as list delimiters (much like quotes delimit strings), if the first thing Perl sees after the function name is `(`, Perl interprets that as the start of a list. The matching `)` will end that list. With out the parentheses, Perl has to look for other syntactic clues to determine the end of the list. The main reason for using parentheses around the arguments to a function is to disambiguate the end of the argument list. Making a special case for the presence of space between the function name and a `(` would re-introduce the ambiguity and break a lot of existing code. Actually, it would be worse because if that `(` were the beginning of a list, the matching `)`, while ending that list, would not be the end of arguments, which would be more confusing. Bottom line, far better to `use warnings;` (and `use strict;`).	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: strange arithmetic
by RonW (Parson) on Jan 09, 2015 at 22:44 UTC

In Perl, functions, including built in functions like print, act like named list operators. So Perl will look for a list of terms and expressions following the name of the function. Because, Perl, ( and ) are used as list delimiters (much like quotes delimit strings), if the first thing Perl sees after the function name is (, Perl interprets that as the start of a list. The matching ) will end that list. With out the parentheses, Perl has to look for other syntactic clues to determine the end of the list. The main reason for using parentheses around the arguments to a function is to disambiguate the end of the argument list.

Making a special case for the presence of space between the function name and a ( would re-introduce the ambiguity and break a lot of existing code. Actually, it would be worse because if that ( were the beginning of a list, the matching ), while ending that list, would not be the end of arguments, which would be more confusing.

Bottom line, far better to use warnings; (and use strict;).

[reply]
[d/l]
[select]