From: "Luca Ferrari"
On Thu, May 9, 2013 at 6:22 PM, Brandon McCaig wrote:
It's a good trait for programmers to avoid waste, but not if it
comes at the expense of reliability, security, or robustness.
Using my() and our() takes very little effort and is well worth
the investment.
Thanks f
On Thu, May 9, 2013 at 6:22 PM, Brandon McCaig wrote:
> It's a good trait for programmers to avoid waste, but not if it
> comes at the expense of reliability, security, or robustness.
> Using my() and our() takes very little effort and is well worth
> the investment.
Thanks for the explanation,
On Thu, May 09, 2013 at 12:15:00PM +0200, Luca Ferrari wrote:
> Hi,
Hello,
> the usage of "my" to scope variables is a good habit, and under
> "strict" is almost a need. But just today I realized that
> having to write "my" in front of each block of variables does
> not seem to me a perl-ish way
Hi Luca,
On Thu, 9 May 2013 12:15:00 +0200
Luca Ferrari wrote:
> Hi,
> the usage of "my" to scope variables is a good habit, and under
> "strict" is almost a need. But just today I realized that having to
> write "my" in front of each block of variables does not seem to me a
> perl-ish way of d
Hi,
the usage of "my" to scope variables is a good habit, and under
"strict" is almost a need. But just today I realized that having to
write "my" in front of each block of variables does not seem to me a
perl-ish way of doing things: it requires extra effort to a quite
simple task (variable decla
