On 7/12/06, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
The perl6 compiler has a custom string type, currently called "Perl6Str". What's the canonically correct mechanism for creating an object of that type?$P0 = new 'Perl6Str' $P0 = new .Perl6Str $P0 = new [ 'Perl6Str' ] At different stages of Parrot development I've seen different answers to this question, so it'd be helpful to know what's "correct". (Also, if the answer is somehow different for Parrot's "built-in" types, such as Undef or Integer, I'd like to know that.)
according to DEPRECATED.pod (not the best place for notes about possible changes (predicted deprecation?)): =item Class name IDs ... will require a dot in front $P0 = new Integer => $P0 = new .Integer according to P6&PE, 2nd edition, PMC variables section (p.188): Unlike PASM, PIR doesn't use a dot in front of the class name. P0 = new PerlString # same as new P0, .PerlString i have no point/counterpoint for the bracketed syntax. hope that provides some history, context, clarification, or confusion. ~jerry
