On Wed, Apr 29, 2009 at 17:20, Gunnar Hjalmarsson wrote:
> Chas. Owens wrote:
>>
>> 2009/4/28 Gunnar Hjalmarsson :
>> snip
>
> I believe the standard response is "patches are welcome."
>>>
>>> Are they? The number of open or "new" bugs at
>>> http://rt.perl.org/rt3/Public/
>>> makes me fe
Chas. Owens wrote:
2009/4/28 Gunnar Hjalmarsson :
snip
I believe the standard response is "patches are welcome."
Are they? The number of open or "new" bugs at http://rt.perl.org/rt3/Public/
makes me fear something else.
( I did submit a bug report a few weeks ago:
http://rt.perl.org/rt3/Publi
Jenda Krynicky wrote:
I think the original problem is with using use strict because 1.
someone told you to or 2. you were told you have to do so for
mod_perl. It's not really "use strict" that's required by mod_perl.
Yep, I agree (and admit).
In either case what wording would you suggest?
M
2009/4/28 Gunnar Hjalmarsson :
snip
>>> I believe the standard response is "patches are welcome."
>
> Are they? The number of open or "new" bugs at http://rt.perl.org/rt3/Public/
> makes me fear something else.
>
> ( I did submit a bug report a few weeks ago:
> http://rt.perl.org/rt3/Public/Bug/Di
From: Gunnar Hjalmarsson
> Jenda Krynicky wrote:
> > From: "Chas. Owens"
> >> On Tue, Apr 28, 2009 at 13:38, Gunnar Hjalmarsson
> >> wrote:
> >> snip
> Fully qualified names do not trip strict. Which is a reason to avoid
> using them. I once work at a place that wrote Perl 5 as if i
Jenda Krynicky wrote:
From: "Chas. Owens"
On Tue, Apr 28, 2009 at 13:38, Gunnar Hjalmarsson wrote:
snip
Fully qualified names do not trip strict. Which is a reason to avoid
using them. I once work at a place that wrote Perl 5 as if it were
still Perl 4. They had turned on strict because th
From: "Chas. Owens"
> On Tue, Apr 28, 2009 at 13:38, Gunnar Hjalmarsson wrote:
> snip
> >> Fully qualified names do not trip strict. Which is a reason to avoid
> >> using them. I once work at a place that wrote Perl 5 as if it were
> >> still Perl 4. They had turned on strict because they had
On Tue, Apr 28, 2009 at 13:38, Gunnar Hjalmarsson wrote:
snip
>> Fully qualified names do not trip strict. Which is a reason to avoid
>> using them. I once work at a place that wrote Perl 5 as if it were
>> still Perl 4. They had turned on strict because they had heard it was
>> the right thing
Chas. Owens wrote:
On Tue, Apr 28, 2009 at 06:36, Dermot wrote:
I saw some code like this today:
!/bin/perl -w
package My::Package;
use strict;
...
%My::Package::somehash = ( keyone => 'val', keytwo => 'val2');
The My::Package::somehash isn't declared as with `my` yet the package
loads withou
On Tue, Apr 28, 2009 at 08:01, Dermot wrote:
>> If no import list is supplied, all possible restrictions are assumed, that
>> why it's working fine
>
>
> Thanx all. I suspected as much. It's not a practise I'd use
> personally. I'm sorry, I don't understand what you mean by "import
> list" here.
> If no import list is supplied, all possible restrictions are assumed, that
> why it's working fine
Thanx all. I suspected as much. It's not a practise I'd use
personally. I'm sorry, I don't understand what you mean by "import
list" here.
Dp.
--
To unsubscribe, e-mail: beginners-unsubscr...@
On Tue, Apr 28, 2009 at 06:36, Dermot wrote:
> Hi,
>
> I saw some code like this today:
>
>
> !/bin/perl -w
>
> package My::Package;
>
> use strict;
> ...
> %My::Package::somehash = ( keyone => 'val', keytwo => 'val2');
>
>
>
> The My::Package::somehash isn't declared as with `my` yet the package
Hi,
I saw some code like this today:
!/bin/perl -w
package My::Package;
use strict;
...
%My::Package::somehash = ( keyone => 'val', keytwo => 'val2');
The My::Package::somehash isn't declared as with `my` yet the package
loads without error or warnings. Is this because the hash is given as
Because you seem to have been asking several questions about scoping and
packages, etc. I found the following link extremely enlightening when
first tackling this subject:
http://perl.plover.com/FAQs/Namespaces.html
http://danconia.org
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additiona
Never mind, I figured it out by put add the $ infront like:
> print $mystuff::a;
> print $mystuff::b;
Hope this help any newbies getting into package.
-rkl
> Can a calling program reference a package variable?
>
> It's not working for me.
>
> test.pl
> ---
> use fruit;
>
> #I want to use thi
Can a calling program reference a package variable?
It's not working for me.
test.pl
---
use fruit;
#I want to use this like a stub or struct
#this does not work - it errored
print mystuff::a;
print mystuff::b;
#this work
mystuff::mixIt;
fruit.pm
--
package mixIt;
$a="apple";
$b=
16 matches
Mail list logo
