comment on

artist wrote:

While it is possible as mentioned, I like to prefer a library of sub routines with specific names, that you can just include in your calling program. It may be easier to maintain and can provide less fear of wrong-doing or less debugging.

Fellow artist
I see this as a distributed library implementation. Would love to know about better ways of implementing this, so I can use this to my own projects.

Maybe the better approach would be to store and retrieve modules from the database, and overload use or require to correctly load your module from the database.

Anyway, I would love to read more about this approach, and about distributed shared perl modules.

-- monsieur_champs

In reply to Re^2: Creating subroutines on the fly by monsieur_champs
in thread Creating subroutines on the fly by pander

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.


Perl Monk, Perl Meditation
	PerlMonks