db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "ModuleVersioningGuidelinesReviewDjd1" by DavidVanCouvering
Date Fri, 23 Sep 2005 17:36:20 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by DavidVanCouvering:

  To answer Craig's concern, I believe you can. Strictly, you don't need the check at all,
you just get a !NoSuchMethodError if you try to invoke a method that does not exist (which
you could catch and ignore but I think that's ugly).
- '''TMNK:''' I'm not sure what module means in this context ... The word module was used
in paper of derby as next. [http://db.apache.org/derby/papers/derby_arch.html#Modules] Are
they, which mentioned in the paper and in this discussion, refer same existance ?
+ '''DVC:''' I moved Tomohito's comments as separate items in ModuleVersioningGuidelinesReview
as I felt they were separate topics from the discussion of version detection and how to decide
if a feature is available.
- Furthermore, what is the code to be shared as module in this discussion ? 
- If it were just java apis, they are shared already ....
+ ----
+ '''DVC:''' Jeremy, can you explain why internalized Strings have more meaning than ints?
 In the code whether they're strings or not they'll be declared as a constant and used as
such in the code.
+ So whether you have {{{public static final String FANCY_FEATURE = "FancyFeature"}}} or {{{public
static final int FANCY_FEATURE = 2}}} it still looks the same in the calling code, e.g. {{{if
CommonModule.implementsFeature(CommonModule.FANCY_FEATURE)}}}.  I prefer ints because then
I could do a simple array and look up by index, and determine if a feature is not implemented
by noticing that the index is out of range. 

View raw message