(tye)Re: Stupid Subclassing Question- Net::ParseWhois

FYI, if its name starts with an underscore, then it is usually an "internal" method which means it was not designed to be overridden and even if you get it working your code is likely to break if the module is upgraded.

Though I haven't verified that Net::ParseWhois is actually following this guideline in this case.

- tye (but my friends call me "Tye")

Comment on (tye)Re: Stupid Subclassing Question- Net::ParseWhois

Replies are listed 'Best First'.
Re: (tye)Re: Stupid Subclassing Question- Net::ParseWhois by pray2s8n (Initiate) on May 15, 2001 at 02:09 UTC
Maybe that's it, 'cause I still can't get it working. I've joined and posted to the netparsewhois list, but right now I'm leaning towards simply pasting my code directly into the original module's _connect() method and remembering to do so each time it is upgraded. This is acceptable to me since I am the exclusive user of the script, machine and modules so why not customize them to my liking? I really need to be able to whois using proxies, and would like to have been able to cleanly override the method rather than hacking it, but my project needs to move forward. Argh.	[reply]
(tye)Re2: Stupid Subclassing Question- Net::ParseWhois by tye (Sage) on May 15, 2001 at 02:15 UTC
In such cases, the best approach might be to patch the module such that it supports adding such capabilities and get the patch incorporated into the module so you don't have to keep repatching the module each time you upgrade it. - tye (but my friends call me "Tye")	[reply]