Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

CromeDome (4395)

  (email not shown publicly)
AOL IM: TheOneCromeDome (Add Buddy, Send Message)

Hello, I'm MrCromeDome from Perl Monks. [] See my account there or my home page for more info.

Journal of CromeDome (4395)

Thursday November 04, 2004
03:59 PM

Naming Conventions

[ #21715 ]

At what point does naming become cumbersome? For example:



DEVNET = my company ;)
PropertyTax = product (as opposed to Recorder, Imaging, etc.)
Parcel = Piece of property
TaxDistricts = Taxing districts a parcel is in

I had started doing DEVNET::PropertyTax::Assessment (for a property's tax assessments) and so forth originally. Then I ran into a problem: I had previously defined DEVNET::PropertyTax::TaxDistricts, which is the listing of all possible tax districts. But now the above seems too lengthy. Is it? What do others do? Am I being too organized?

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • But now the above seems too lengthy.

    I've often seen people remark about long names (tho usually with function/method calls).

    Personally, I don't worry about it when it comes to modules. I try to organize them in a manner that makes it easy for me to find the code I need to work on.

    That is my sole naming criteria. It has to make sense so I can find my code.

    As for length... well, I only have to type the module name twice. Once for the use clause, and once for the new statement.

    After that, I use the objec
  • Abbreviate the company name and project.