in reply to Re: checking a method is not subclassed
in thread checking a method is not subclassed

if you really want to do it, you can use a CHECK block to browse all the symbol tables once all the modules and the script have been loaded and parsed, examining with packages subclass your special classes and that they don't redefine the methods you want to protect.

You can even use a subrutine attribute to do it (as :final).

Though modules could still work around that defining new methods at runtime via eval or just playing with the symbol tables.

Replies are listed 'Best First'.
Re^3: checking a method is not subclassed
by water (Deacon) on Feb 02, 2006 at 17:51 UTC
    This sounds interesting. Yeah, I know others can use eval and play games with the symbol table at runtime. Leaving out those may-I-call-them pathological cases, could you say more about your approach?