Dan Sugalski writes: > If the vtable stuff goes into the core perl engine (and it probably will, > barring performance issues), then what could happen in the I have a lot of questions. Please point me to the appropriate place if they are answered elsewhere. vtables are tables of C functions? Perl functions? Either? How would you use them to handle overloading of operators? One function in the vtable for every operation? How does that extend to user-defined operators? Nat
- Re: RFC 161 (v2) OO Integration/Mi... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migration P... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migrati... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/Migrati... Bart Lateur
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Torkington
- Re: RFC 161 (v2) OO Integration/Migration P... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migrati... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/Mi... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Torkington
- Re: RFC 161 (v2) OO Integration/Migration Path Dan Sugalski
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Torkington
- Re: RFC 161 (v2) OO Integration/Migration P... Dan Sugalski
- Re: RFC 161 (v2) OO Integration/Migration P... Nick Ing-Simmons
- Re: RFC 161 (v2) OO Integration/Migration Path Steve Fink
- Re: RFC 161 (v2) OO Integration/Migration P... Dan Sugalski
- Re: RFC 161 (v2) OO Integration/Migration P... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Wiger