Conor Walsh writes:
> I thought Perl 6 was supposed to fix the DWIM bug.
IIRC, I read the other day it narrows it so that only an assignment to a
data structure element autovivifies but an attempted access does
not. That would eliminate some do what I don't mean cases, eh?
--
Mike Small
sma...
I thought Perl 6 was supposed to fix the DWIM bug.
On Wed, Nov 9, 2016 at 3:38 PM, Bill Ricker wrote:
> On Wed, Nov 9, 2016 at 3:24 PM, Mike Small wrote:
>> I have trouble
>> remembering the handy special cases but when it's somewhat systematic
>> that helps.
>
> yeah, the DWIM magic is really n
On Wed, Nov 9, 2016 at 3:24 PM, Mike Small wrote:
> I have trouble
> remembering the handy special cases but when it's somewhat systematic
> that helps.
yeah, the DWIM magic is really nice when it really is what we meant,
but is surprising when it's internally consistent in it's own special
way,
On 11/09/2016 03:24 PM, Mike Small wrote:
Uri Guttman writes:
On 11/09/2016 02:04 PM, Bill Ricker wrote:
I think Uri and Ricky have it nailed.
You can
wrap with do{ no warnings; ... } or
protect the concatenation with 42 . ($b//q()); or equivalent ?: or or
use $b .= 42 ; if order doesn't
Uri Guttman writes:
> On 11/09/2016 02:04 PM, Bill Ricker wrote:
>> I think Uri and Ricky have it nailed.
>>
>> You can
>> wrap with do{ no warnings; ... } or
>> protect the concatenation with 42 . ($b//q()); or equivalent ?: or or
>> use $b .= 42 ; if order doesn't matter (it usually does, th
On 11/09/2016 02:04 PM, Bill Ricker wrote:
I think Uri and Ricky have it nailed.
You can
wrap with do{ no warnings; ... } or
protect the concatenation with 42 . ($b//q()); or equivalent ?: or or
use $b .= 42 ; if order doesn't matter (it usually does, though)
or initialized $b to '' instead o
I think Uri and Ricky have it nailed.
You can
wrap with do{ no warnings; ... } or
protect the concatenation with 42 . ($b//q()); or equivalent ?: or or
use $b .= 42 ; if order doesn't matter (it usually does, though)
or initialized $b to '' instead of undef, knowing it will be
concatenated (but
On 11/09/2016 01:40 PM, Morse, Richard E.,MGH wrote:
On Nov 9, 2016, at 12:49 PM, Mike Small wrote:
#!/usr/pkg/bin/perl
use warnings;
my $a;
$a .= '70';
my $b;
$b = 42 . $b;
print "$a, $b\n";
With the script above I get an uninitialized value warning from perl
5.24 for the second concatenat
> On Nov 9, 2016, at 12:49 PM, Mike Small wrote:
>
>
> #!/usr/pkg/bin/perl
> use warnings;
>
> my $a;
> $a .= '70';
> my $b;
> $b = 42 . $b;
> print "$a, $b\n";
>
>
> With the script above I get an uninitialized value warning from perl
> 5.24 for the second concatenation but not the first. Is
#!/usr/pkg/bin/perl
use warnings;
my $a;
$a .= '70';
my $b;
$b = 42 . $b;
print "$a, $b\n";
With the script above I get an uninitialized value warning from perl
5.24 for the second concatenation but not the first. Is there a story
behind this? Something to do with the first case being something
10 matches
Mail list logo