Re^2: Why is "odd number of elements in hash assignment" warning and not error?

> at least people are getting a warning in the first place,

yep, as a side note:

"devision by 0" is a "silent Not_a_Number" in some languages like JS

I.e. not a fatal stop of execution!

Not any exception which could be activated or caught!

Just returning "NaN" from calculation.

> there's the "thanks for the warning but I know what I'm doing" crowd,

And we had recently a discussion about people complaining that undefined values raise far too many warnings. ;-)

> > why "misc" category and not, say, "hash"/"odd"?!?!

> That is an excellent point

most likely the set of warnings was expanded gradually over time...

update

> worthy of a patch or at least feature request to P5P.

well I'm more concerned that obvious compile time errors aren't reported

perl -we 'sub tst {%h=\%h}'

(reusing %h to silence "only used one")

Cheers Rolf

PS: Je suis Charlie!

Comment on Re^2: Why is "odd number of elements in hash assignment" warning and not error? Download Code

Replies are listed 'Best First'.
Re^3: Why is "odd number of elements in hash assignment" warning and not error? by Anonymous Monk on Feb 18, 2015 at 18:38 UTC
Just to throw in another side note :-) And we had recently a discussion about people complaining that undefined values raise far too many warnings. ;-) Even here, I think giving the programmer control is the best option: When I'm generating stuff from templates, I often use `no warnings 'uninitialized';` because I want my `undef`s to silently become `""`, but when I'm handling other data, e.g. from a database where there is a difference between `NULL` and `0.0`, I prefer having the warnings (and once in a while I may even fatalize them).	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: Why is "odd number of elements in hash assignment" warning and not error?
by Anonymous Monk on Feb 18, 2015 at 18:38 UTC

Just to throw in another side note :-)

And we had recently a discussion about people complaining that undefined values raise far too many warnings. ;-)

Even here, I think giving the programmer control is the best option: When I'm generating stuff from templates, I often use no warnings 'uninitialized'; because I want my undefs to silently become "", but when I'm handling other data, e.g. from a database where there is a difference between NULL and 0.0, I prefer having the warnings (and once in a while I may even fatalize them).

[reply]
[d/l]
[select]