demerphq oryiufjngmailcom 102907 linda w wrote function forward referenced defined already semiexists state im saying function quasi state shouldnt override parental lookup machinery bug brought table 929 thats month ago nobody clue local undefined methods would stop perls oo lookup machinery working er code first posted wasnt happening calling subroutine stubs package reference werent even proper oo dispatch stop spreading incorrect meme stops perls oo dispatch working properly works properly exactly designed speced fact means doesnt expected something entirely different hand strongly suspect one encounter im first person decided work around buggy code like everyone else dont use references use strings method calls sounded superstitious wanted know wrong code around sounded superstitious listen advice several experienced perl programmers sounds superstitious listen people telling wrong correct way problems encountering wouldnt occur perl dynamic language references hard binding method names string loose binding adds fact take reference method point later time reference may longer correspond would happen use proper method dispatch ie string based kind problem doesnt arise static languages full class heirarchy known compile time well said perl dymanic language example sub foo print foo foo local foosub print bar foo take reference foo point called first code execute point foo called second time youll see isnt sub would executed calling foo name sub foo print foo foo subfoo local foosub print bar foo sub string name method dispatch works references methods dont work reliably anyway superstitious way things work dynamic language find bug big enough drive truck many people suggested ways work around bug pushed back examples things didnt work people stopped responding important things going perlbug hunt knew work around accepted way things taking reference would activate bug waste time tracking code broken mean ill say stopped responding appeared wasting time helping time limited even limited prefer waste probably shouldnt even writing gave several clear reasons code buggy wrong persisted insisting right work even though er doesnt work isnt right least perl truly dynamic language think arguing people explaining misunderstandings good way get things done fine dont get upset people dont play along behavior experienced perlcoders knew instinctively way work around indicates knew code around buggy area none able tell part code incorrect contrary explained incorrect argued seems much ddtt situation ddtt dont thing regardless people reactions probing month dont think case infrequent would like believe one willing deal flack dont know arent willing take help ie willing code differently understanding cant make shit expect computer want yes infrequent first time ever encountered someone expected able take reference subroutine defined one package referencing named subroutine different package relationship two entry isa array expect work fact adverse affect results perls method dispatch mechanism reason dont yves props mark jason dominus perl mredebug e justanotherperlhacker thu 07 aug 2008 075952 0100 broken ooparentmethod call