Re: •Re: Re: Re^3: VarStructor 1.0

[Wassercrats]

I'm more receptive to recommendations than you all think, but I'd prefer those recommendations to involve more than style. I'd rather have a module that I don't have to learn to understand, especially since I'd be expected to maintain it, than one that's easier for others to understand. When it comes to my parameter handling vs. tkil's, and using strict and "my" and stuff, I'd just as soon have everyone downvote me than change, unless I hear something more substantial about why the change would be beneficial and not just unsupported claims that it would be easier for me and safer.

When it comes to people saying that my module wouldn't be useful, it's hard to believe that because VarStructor has some advantages over Xref, and people have no problem with Xref, but that doesn't matter any more because I intend to turn VarStructor into a commercial product, described at Re: Do not feed the trolls.... The variable values it displays would be as they are within the blocks they're scoped to, and I'll also have it optionally work with all used modules. Then you'll all be sending me money and gifts and naming your children after me because I'd have a unique, indispensable debugging tool that revolutionizes Perl programming.

And they'll be TWO dots next to my posts!