perhaps i'm flogging a dead horse here, but isn't
com.sun.org.apache.xerces.internal.jaxp.datatype.DatatypeFactoryImpl
just plain daft?
On 17/06/05 14:02 Marsh-Bourdon, Christopher wrote:
I favour using org.apache.* or com.sun.*, but never com.microsoft.*. It
gives a certain gravitas to one's coding! ;-)
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: 17 June 2005 13:59
To: Struts Users Mailing List
Subject: Re: [OT] package naming nonsense
1. Well, no one suggested that you need to search some archive.
2. It would be difficult (if not impossible) to name an example of an
application that has a namespace collision that is publicly available. I
hope you understand why.
Finally, naming conventions are not enforced by compilers. Name your
packages as you wish.
-Dennis
Adam Hardy <[EMAIL PROTECTED]>
06/17/2005 08:48 AM
Please respond to
"Struts Users Mailing List" <user@struts.apache.org>
To
Struts Users Mailing List <user@struts.apache.org>
cc
Subject
Re: [OT] package naming nonsense
OK, silly me, I started using java with 1.2, rather than 1.0, but it's
friday, so please don't tell me to go read the archives!!!!
I admit, in theory it's easy to say, you're using blah.blah.blah.foo and
so am I, a disaster in the making, but when is that going to happen? I
challenge you to name me an example. Take eBay for example. They just
went off and bought up all the top level domains for ebay.
What bugs me is that the low correlation between java programs and the
top level domains.
Oh hell, I just wish I had 5 grand to buy ecoworks.com :-(
On 17/06/05 13:17 [EMAIL PROTECTED] wrote:
Why, just the other day, I contemplated the same thing. In fact, I TOO
named my OSS package blah.blah.blah. But wait, what would've happened
if
you and I had not only the same package structure, but also 2 classes
with
the same name e.g. blah.blah.blah.foo, and you decided to use my OSS?
I'm guessing that you haven't been using Java very long, because the
issue
of namespace collision was well discussed when 1.0 came out. Hopefully,
you understand why you're suggestion is sil...er, not feasible.
-Dennis
Adam Hardy <[EMAIL PROTECTED]>
06/17/2005 07:46 AM
Please respond to
"Struts Users Mailing List" <user@struts.apache.org>
To
Struts Users Mailing List <user@struts.apache.org>
cc
Subject
[OT] package naming nonsense
Since it's Friday and I'm just about to start a new project, I thought
I'd ask everyone what they think about something that's always bugged
me.
Package names in Java. Why do we all have com.blah.blah or
org.apache.stuff.xxx instead of just plain blah.blah.blah and
apache.stuff.xxx?
What really got me on my last project was changing from one organisation
to another, the project packages had to be renamed from uk.co.bbb to
com.siemans and we actually made it all the more pointless by discussing
whether it should be com.siemenz or de.siemenz.
I'd love to drop the whole top-level domain but why on earth is it there
in the first place?
My new project is for a charity ecoworks with the top-level domain .eu
and they might even purchase ecoworks.org too, and I don't want to mess
around, so why can't I just have my packages like this:
ecoworks.forum.etc
ecoworks.newsfeed.etc
instead of eu.ecoworks or eu.ecoworks or whatever.
And why isn't it just plain apache.struts or apache.tomcat? It's not as
though there's ever going to be a mix up with code like com.apache. - or
is there?
And even if there is, why is the mix-up possibility so important when it
comes to package names, when it's not considered when it comes to jar
naming conventions. If there ever was a com.apache.struts, what would
they call their jar? Would they have to use com_struts-1.2.7.jar
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
