comment on

> Are you sure you just don't want to install an AUTOLOAD routine?

I was thinking about that. I ran into two problems, however.

1) I still want to have things set themselves up with "use", so that the caller of my module does not have to mess with my modules internal functions (which he would have if he wanted to write an AUTOLOAD). So I was thinking to export an AUTOLOAD into the caller's namespace, but maybe that is evil.

2) What I am really trying to do is make Oracle PL/SQL procedures appear like Perl procedures. PL/SQL procedures can have characters in them that are not allowed for Perl subroutines, most importantly a dot. If my Oracle function is called dbms_random.random, I can map that to a Perl function dbms_random_random, but that is a one-way mapping: An AUTOLOAD for dbms_random_random has no (easy) way to figure out if it is supposed to call dbms_random.random or dbms.random_random.

Anyway, looking at AUTOLOAD was really worthwhile, makes one appreciate Perl even more.

In reply to Re^2: Using import to generate subroutines by Thilosophy
in thread Using import to generate subroutines by Thilosophy

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Pathologically Eclectic Rubbish Lister
	PerlMonks