From: Mark Hahn Date: 2001-12-06T15:24:38+09:00 Subject: [ruby-talk:27646] Re: Package Naming I'm confused. You were saying you didn't like the deep hierarchy and now you are saying it was needed. How would some other short scheme help you if you had to have the long one anyway? What am I missing? What are you arguing for? -----Original Message----- From: Sean Russell [mailto:ser@germane-software.com] Sent: Wednesday, December 05, 2001 8:53 PM To: ruby-talk ML; undisclosed-recipients: Subject: [ruby-talk:27616] Re: Package Naming Mark Hahn wrote: > Your names could have easily been us.fed.fs.Sorting also. Not really. Having only one Sorting package in the entire USA Federal Govornment is extremely unlikely. In fact, each of the path levels is important. The number of people working within NRIS is a few hundred working all across the country, so even us.fed.fs.nris is too big to be able to avoid conflicts. We might be able to get away with us.fed.fs.nris.tools, but there are 6 different Analysis tools projects, none of which share any common code, so us.fed.fs.nris.tools.etools (representing one distinct set of analysis tools) is better. Of course, ETools has a client and a server component, and we could probably dump all 386 classes into one big namespace under ETools, but this would be really messy. We *might* be able to put the analysis tools projects directly under the NRIS namespace, but by then, the package name is already too long for convenient use. -- --- SER