pagaltzis passdelwxgmxde gerard goossen 20071107 2115 strange actually rigidity language natural language background claiming dwim guess currently stands somebody 10 years ago perls original culture sysadmin world surprise stability enjoys ultimate priority among goals courage say might crazy errorprone etc way currently works stuck part say better worse regarding autovivification method resolution respecting stubs hack put deal autoload limitations way fix problem causes hacking hack said two problems make whole oomethodresolution lot sane method resolution red herring issue hand stubs forward references perl 5 preserve enough information time stub creationforward ref taking later able distinguish would like skip undef subs already suggested allow forward declarations remove forward declarations seems really need even stubs remove autoload people supposed write proxy objects without autoload classes closed default kurila acquires sane reflection facilities guess could use reflection create methods needed open classes seem like option possible anymore class whose instances proxy objects different classes things like objecttrampoline job could create mechanism code notified changes class guess proxies could modify response modifications proxied classes classes whose instances need proxy instances different classes could create new proxy classes runtime suppose im sure would possible sanely compose proxies anymore though also efficient something else already thought maybe possibly already approach mind address regards aristotle pagaltzis thu 07 aug 2008 193337 0100 perl 47181 try oo semantics throwing fatal error