chromatic wrote:
So I'm interested in hearing what pushes Arrays and Hashes over the edge for needing their own container and sigil, whereas Junctions/Sets do not.
Perl isn't a "pure" object-oriented language.
Rephrasing my question:
What characteristics would _any_ new structure or class have to have to merit becoming a first class container with it's own sigil, rather than being just another class?
Or is Perl close enough to "pure" object-oriented these days, where only grandfathered classes make the cut?
As a separate question, is there a relatively easy way to create a user-defined class with it's own sigil? (w/o having to modify half the parse rules).
-- Rod Adams
