comment on

Perhaps it would be wise to call it "Termkey::Xyzzy" until it's written and then to see what name seems appropriate after you've reviewed the working code?

After all, until you release it to others, it is for personal use.

The suggestion isn't a facetious as it sounds. The idea being to get the current problem solved, see what you used to solve it, and then improve those tools when there's some breathing space and experience. Yes, it's nice to know things up front. OTOH, you only get permission to build version 2.0 when the client is satisfied with version 1.0. If this problem is keeping you from getting the work done, then defer it, do the work, and then come back to it. You may find the problem has solved itself by then. If it hasn't, well, at least you haven't wasted your client's and/or sponsor's time on it.

--f

In reply to Re: Module Naming Conventions by footpad
in thread Module Naming Conventions by jlongino

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