text_combined: linda w twaxvptwszvtlinxorg nicholas clark via rt wrote many parts perl implementation considered broken still seem work well enough eh guess havent run subconsciously inculcated proper methods hit methods subroutines could considered one fact take reference yet undeclared subroutine another one wellpersonally dont recall bug per se perl dynamic language undeclared subroutine could declared runtime eval becomes subroutines caught autoload around p6 isnt construction nonexistent subroutines could follow predetermined naming convention accessors considered useful feature using autoload perhaps gracefully recover might otherwise fatal error seem remember pseudoperlshells undefined procedures could tried autoload function external executables perl 6 decided latter right perl 6 taking reference undeclared subroutine method distinct compile time error sigh ive never used construct intentionally anyway dynamic language seems like could useful feature best worlds controllable via pragma perhaps allowing case one could provide res describe undefined subroutine patterns wouldnt considered error would allow autoload type handler called maybe change perl 5 wouldnt kick 514 though would deprecation warning 512 510 nearly upon us people said using reason perhaps want typing autoloaded functions truly widely used feature id hate see something like go away either unnecessarily without provision backward compatibility believe mentioned least thought head though typed use pragma type operation could specify whether give ancestor functionchecking priority autoload autoload would checked first fails check ancestors possible matching methods afaik autoload isnt oofeature imo orthogonal feature simply isnt part generic oo specification may still great use perl5 planning rewrite parts ooplayground program one think broken use autoload specifically similarly structured access functions point wed solve problem surprising run time behaviour agreed might prevented hitting head wall behaviour part indicated desire solution solves particular pitfall fell might harm others relying form behaviour especially use widespread vehemently assert dont problem undef function may may resolved runtime actions taken isnt resolved runtime wrespect oostructured calls blessrefmethod addressing nonoo call case one piece functionality missing might providable idea can_autoload type call providable helper function autoload example using autoload provide accessor functions can_autoload func could check allowed fields return defined undefined can_autoload would depend user autoload adding extra code new modules wanted use outside scope particular problem believe idea world printed notyetdefinedfunc using print autoload fails undef substituted perhaps dont see use autovivifying functions ever fully defined never work attempts define runtime fail depending context anotyetdefinedfunc vs trying call could return undef someone tries call would necessary generate attempt call undefined subroutinefatal error used rvalue would rather see undef subbed least seems like would provide todays functionality backward compatible way im open mind changed point would seem possible logical outcome calling undefined function nonoo way notyetdefinedfunca isnt something trying suggest fix current ooproblem case describe related issue exactly topic problem describing particular problem report perl made runtimeresolution decisions regarding notfullydefined methods functions seems might eliminate problem ran hard think handling nonoo case would affect backward compatibility im focusing oocall syntax side problem fixing way describe might solve issue im sure great disallowing compiletime undefined function stubs taking address would affect existing base code wanted voice opinion im suggesting throw baby bathwaterso speak linda fri 08 aug 2008 030449 0800 perl 47181 try oo semantics throwing fatal error