Re^3: Template::Toolkit: defined on aggregate item vs. defined on variable

Because arrays start at 0? So group.1 is not defined? And the condition is true?

if( 1 ne "") { 
   print "Seems like a bug! BUT IT IS NOT BUG\n";
}
[download]

Comment on Re^3: Template::Toolkit: defined on aggregate item vs. defined on variable Download Code

Replies are listed 'Best First'.
Re^4: Template::Toolkit: defined on aggregate item vs. defined on variable by choroba (Cardinal) on Aug 05, 2016 at 22:40 UTC
But why is `g` defined, when `g = group.1` and, as you said, `group.1` is not defined? ($q=q:Sq=~/;[c](.)(.)/;chr(-\|\|-\|5+lengthSq)`"S\|oS2"`map{chr \|+ord }map{substrSq`S_+\|`\|}3E\|-\|`7**2-3:)=~y+S\|`+$1,++print+eval$q,q,a, [download]	[reply] [d/l] [select]
Re^5: Template::Toolkit: defined on aggregate item vs. defined on variable (STRICT) by beech (Parson) on Aug 06, 2016 at 00:57 UTC
:D awesome now I'm getting it Autovivification? This is the code `$stash->set('g', $stash->get(['group', 0, 1, 0]));` [download] So testing it outside of tpage , it returns empty string instead of undef Read more... (2 kB) None of the various https://metacpan.org/source/ABW/Template-Toolkit-2.26/t/stash.t seem to test defined But docs show https://metacpan.org/pod/Template::Stash#undefined-ident-args which links https://metacpan.org/pod/Template::Manual::Config#STRICT Which says its a regrettable design decision, so I guess not a bug tpage/ttree don't have / take a -template_strict option	[reply] [d/l] [select]