in reply to Module Naming Conventions
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
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: Module Naming Conventions
by jlongino (Parson) on Sep 03, 2001 at 08:46 UTC |