in reply to Re: Situation where warning "Found = in conditional, should be" seems obsolete
in thread Situation where warning "Found = in conditional, should be" seems obsolete
Hello.
I will spend (waste?) more time for answer this thread. You may not interpret that code as obfuscated or intentionally obfuscated. Secondly obfuscation is a point of view, e.g. it depends on reading/writing style, which differs as Perl greets TMTOWTDI idiom; and it depends on demands of maintainability (which are not mentioned in this node).
This node is not about obfuscation nor about code maintenance. It is more about warning, its significance and about operators which throws it.
I will spend (waste?) more time for answer this thread. You may not interpret that code as obfuscated or intentionally obfuscated. Secondly obfuscation is a point of view, e.g. it depends on reading/writing style, which differs as Perl greets TMTOWTDI idiom; and it depends on demands of maintainability (which are not mentioned in this node).
This node is not about obfuscation nor about code maintenance. It is more about warning, its significance and about operators which throws it.
In Section
Seekers of Perl Wisdom