Re: Reoccuring message


good chemistry is complicated, and a little bit messy -LW
	PerlMonks

Re: Reoccuring message

by Bloodnok (Vicar)

on Jun 09, 2014 at 12:06 UTC ( [id://1089258]=note: print w/replies, xml )

Need Help??

in reply to Reoccuring message

Although use strict; is highly recommended (almost to the point of mandated:-) by monks far more knowledgeable than me, in this case, the behaviour would be identical to that observed - which, IMHO, might provide a use case for the improvement of perl itself by way of identifying the variable that it considers to be read-only within the error message - sometimes I've struggled to try and spot problems such as this.

Anyway, in for ($1 = 0; $i <= 10; $i++) {, you assign a value of 0 to $1, methinx that you meant to write for ($i = 0; $i <= 10; $i++) {, or even for (my $i = 0; $i <= 10; $i++) {.

I would also point out that, strictly speaking, the message isn't Reoccuring since it only occurs once per run.

Update:

Thanx to AnomalousMonk (I do like like name:-), added my to 2nd suggestion.

A user level that continues to overstate my experience :-))

Comment on Re: Reoccuring message Select or Download Code

Replies are listed 'Best First'.

Re^2: Reoccuring message
by Lotus1 (Vicar) on Sep 07, 2018 at 02:35 UTC

Although use strict; is highly recommended [...] in this case, the behaviour would be identical to that observed [...]

Hi Bloodnok. If you add use strict; to the program from the OP then you get errors for the undeclared variables. After you add 'my' to declare them as lexical variables you get an error 'Can't use global $1 in "my" at C:\path\997292.pl line 7, near "my $1 ".'

Edit: Here are some discussions about using the strict pragma. Use strict and warnings, strict, https://www.perl.com/pub/2001/01/begperl6.html/#use%20strict, Why We Use Strict!, https://perlmaven.com/strict.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom