This is the mail archive of the docbook@lists.oasis-open.org mailing list for the DocBook project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Re: packagename proposal/RFE


From: Jirka Kosek <jirka@kosek.cz>
To: "Matt G." <matt_g_@hotmail.com>
CC: docbook@lists.oasis-open.org
Subject: Re: DOCBOOK: Re: packagename proposal/RFE
Date: Wed, 05 Jun 2002 13:11:43 +0200

"Matt G." wrote:

> >e.g. C++ or C# namespaces or Perl modules?
>
> Arg! Please don't confuse namespaces and packages!! Even though Java may

In .Net (C#, VB.NET, ...) terminology namespace is equivalent to package
in Java sense. It is set of related classes. It's quite confusing name,
but it's here. Using <package> for Java package, C# namespace, Perl/PHP
module, Pascal/Delphi unit, ... seems reasonable.
I think we're in agreement, here. I just want to clarify that the two are distinct and independent concepts. It's just that, in the languages you mentioned, they're coupled, as a result of the fact that packages get a unique namespace. Therefore, one could effectively use the terms interchangeably, within any of those contexts (though it might be confusing, to actually do so).

Personally, I believe it might be worth adding a 'namespace' element, for purposes other than referring to a Java "package" (or similar constructs, in other languages). One could certainly use this hypothetical 'namespace' element, to markup a reference to the namespace defined by a Java package (or similar, in C#), but a separate 'namespace' element is really necessitated by cases such as C++ and XML, for which no equivalent exists.


Matt


_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]