G'day haj,
++ Thanks for looking into the points I raised and providing feedback.
There wasn't anything that was actually "scary", at least for me. I usually try out experimental features privately when they first appear; I won't use them in production (personal, $work, or even PM code) until the experimental status is lifted. I wasn't too surprised with "very incomplete": I took class to be the first step in a staged implementation, wholly or partly, of Corinna.
What you wrote about parent presumably also applies to base and any code that manipulates @ISA (either directly or via a module).
That's an interesting point about package and class names. I had wondered about that but didn't list it with things I was interested in testing. Forbidding duplicate names seems appropriate; although, presumably something like this would be valid (even if it is poor design):
class X; ... package Y; ... class X; ... extend the class here ...
— Ken
In reply to Re^3: Thoughts on new 'class' OO in upcoming perl
by kcott
in thread Thoughts on new 'class' OO in upcoming perl
by cavac
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |