> Great. My point I was trying to drive at was that: > > my int $x = 5; > > Could turn around and do something different than asInt(). All stores Got it. And sure, why not? Pay the overhead when you absolutely need to, and no sooner. The core idea (for me) is to avoid wasting resources on a meta-type if you don't need to. So an int gets stored as two bytes and not four or eight. This way you wouldn't have to convert *to* meta and then *from* meta format. Essentially, if you say what you mean, Perl will work better for you. And DWIM is always there to back you up, if need be. (I know you get this -- I just want to spell it out better so that no one misunderstands my intent.) And to clarify further for others: this would be *strictly voluntary*. Perl can still do all the work for you if you want! > At the very least we know there's two crazy people on this list! At least until my meds kick in! Matt
- RFC 161 (v2) OO Integration/Migration Path Perl6 RFC Librarian
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Wiger
- Re: RFC 161 (v2) OO Integration/Migration Pat... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migration... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/Migra... Nathan Torkington
- Re: RFC 161 (v2) OO Integration/... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/... Randal L. Schwartz
- Re: RFC 161 (v2) OO Integrat... Nathan Wiger
- Re: RFC 161 (v2) OO Integrat... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migra... Matt Youell
- Re: RFC 161 (v2) OO Integration/... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/... Bart Lateur
- Re: RFC 161 (v2) OO Integration/Migration... Nathan Torkington
- Re: RFC 161 (v2) OO Integration/Migra... Matt Youell
- Re: RFC 161 (v2) OO Integration/... Nathan Wiger
- Re: RFC 161 (v2) OO Integrat... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Torkington
- Re: RFC 161 (v2) OO Integration/Migration Pat... Dan Sugalski
- Re: RFC 161 (v2) OO Integration/Migration... Steve Fink
- Re: RFC 161 (v2) OO Integration/Migra... Dan Sugalski