in reply to Tied variables and functions for them

Hm. I like your idea, in some respects, but think the implementation sucks. The idea of exporting functions has no place mixing with object-orented programming, and tied stuff is the ultimate in OOP. (Note: this can either imply that I like both or hate both. That's quite on purpose.)

The way you do this makes Tie::ArrayXYZ more difficult to subclass properly (perhaps not; I havn't looked that deeply. You use isa, which is a good sign), but more importantly, it makes it impossible to name your functions reasonably, since you can't have a methodfunction for the tied object and have a normal function (or even a mehtodfunction of a different tied object) at the same time, since your screwing with your users' namespace. IMHO, what you should be doing is making @tiedarray->mehtod DWIM, which would probably require a METHODCALL tie function.

BTW, rereading this after preview before submit, I noticed that it sounds rather harsh. I didn't mean for it to come out that way, it's just been that kind of qw(day, month, year, lifetime)[rand 3].

-- 
James Mastros, AIM:theorbtwo, PM:theorbtwo, EMAIL:theorb@iname.com

In Section Meditations