Re^2: "Experimental push on scalar is now forbidden"

Thank you for your observations. But I do not think that it is a matter of attitude. I would define it as a matter of temperament, or of view of the world. I am perfectly willing to pay the price of nostrictness nowarningness. Indeed, I am saddened when I fire up, say, re.pl, I input something like:

$a = $b + $c
[download]

and get the response:

Compile error: Global symbol "$c" requires explicit package name (did 
+you forget to declare "my $c"?) at (eval 323) line 5.
BEGIN not safe after errors--compilation aborted at (eval 323) line 5.
[download]

Is this a big problem for me? Not at all, as soon as I am allowed to begin a program with "no strict; no warnings;". Thank you for your understanding and your willingness to be of help. Best regards Gian Luca

Comment on Re^2: "Experimental push on scalar is now forbidden" Select or Download Code

Replies are listed 'Best First'.
Re^3: "Experimental push on scalar is now forbidden" by eyepopslikeamosquito (Archbishop) on Dec 21, 2021 at 02:59 UTC
I am saddened when I fire up, say, re.pl, I input something like: `$a = $b + $c` ... You really shouldn't be using `$a` and `$b` like this. :) As noted in perlvar, these two variables are treated specially by Perl. Though fine in sort blocks (for which they were designed), you should avoid them in regular code so as to avoid unnecessary grey hairs, and wasting time, for example wondering why on earth did Perl complain about `$c` in your sample code, but not `$a` or `$b`? But I do not think that it is a matter of attitude. I would define it as a matter of temperament, or of view of the world. I am perfectly willing to pay the price of nostrictness nowarningness. While Larry might applaud your individualism (he invented TMTOWTDI after all), I don't like your chances of finding teammates willing to embrace your view of the world. At least, your nostrictness nowarningness world view would last about 5 nanoseconds on any team I've ever worked in. :) To illustrate where I'm coming from see: Why Create Coding Standards and Perform Code Reviews? Update:: Found a Perl Monk who'd be delighted to work in your team.	[reply] [d/l] [select]
Re^3: "Experimental push on scalar is now forbidden" by Marshall (Canon) on Dec 21, 2021 at 05:11 UTC
I don't know what "I am perfectly willing to pay the price of nostrictness nowarningness" means? For me that would mean less reliable and harder to debug code. I like code that works and anything that furthers that objective is, in my opinion, good. I personally don't enjoy spending hours finding a simple typographical mistake. I was also taken aback by "Experimental push on scalar is now forbidden at ... line 7582, near "} )". 7K+ lines of Perl is a heck of a lot of code in a single compilation module! There are ways to separate this into logical units. But this is a forum of the willing. If you ever desire to know how to do this, ask. The Monks will help.	[reply]