xt
发帖数: 17532 | 1
Yes, this works, but it is not a good idea.
First, it does not make sense to implement a constant interface.
Interface means ADT, and what does a constant interface mean?
Second, implementing such an interface gives rise to naming
clashes. For example:
public interface A {
public static final int a = 1;
}
public interface B {
public static final int a = 2;
}
If you implement both interfaces, there you have to think how
the a is evaluated. If you want to be specific, A.a, B.a is better
w | xt
发帖数: 17532 | 2 Just some personal follow up ideas:
It does not kill you if you type a little more to make the program
more readable and better in style. We have been using vi editor
to write everything (excluding GUI design sometimes, but some
people actually write PowerJ scripts with vi instead of using
the PowerJ GUI to design frames as well. Even my co-op student
knows how to do it). Implementing interfaces with nothing but
constants is bad idea in terms of software engineering.
More typing may cost you tim
【在 xt 的大作中提到】
:
: Yes, this works, but it is not a good idea.
: First, it does not make sense to implement a constant interface.
: Interface means ADT, and what does a constant interface mean?
: Second, implementing such an interface gives rise to naming
: clashes. For example:
: public interface A {
: public static final int a = 1;
: }
: public interface B {
| m******t
发帖数: 2416 | 3 I am with xt on this one. The basic point is, think about it
in OO way, that is, constants are also part of your data, rather
than just some macros in C. And you need to organize and encapsulate
your data into classes.
If you have either a good memory(which I don't have), or an IDE
supporting abbreviation/auto completion(which I do), typing long
variable names is never a big problem. 8-) | m******t
发帖数: 2416 | 4 Forte Community Edition is a commercial wrap-up for Netbeans.
Netbeans is open-source, but sponsored by Sun(that is, Sun is
cutting the pay checks)
Sun is planning on releasing the Prof. and Ent. Edition. But
won't be free.
I'd suggest you to go to www.netbeans.org. and download
Netbeans 3.0. It's a full-fledged Java IDE. | m*****e
发帖数: 126 | 5 I do not agree with some of your points.
1. Sometimes it is good practice to use interface to define constants.
A good example in JDK is the SwingConstants interface. It defined
many constants which are used elsewhere in javax.swing package.
2. About the naming confusion, I think the programer should be responsible
for this. If a programmer always names his variables as things like
'a' or 'b', surely he will have trouble from time to time.
3. If we name the constants properly, there | m******t
发帖数: 2416 | 6
First of all, while we all agree the Java core classes can be used
as classic examples for certain patterns or feature usage, not every
single bit of them is so "holy" and indisputable.
In the case of SwingConstants (and also some IO classes mentioned
in some previous post), the purpose of this separate interface is
to define constants that are used in so many swing classes that it is
inappropriate to define them repeatedly in all those classes. However,
the designer didn't put *all* constants
【在 m*****e 的大作中提到】
: I do not agree with some of your points.
: 1. Sometimes it is good practice to use interface to define constants.
: A good example in JDK is the SwingConstants interface. It defined
: many constants which are used elsewhere in javax.swing package.
: 2. About the naming confusion, I think the programer should be responsible
: for this. If a programmer always names his variables as things like
: 'a' or 'b', surely he will have trouble from time to time.
: 3. If we name the constants properly, there
| xt
发帖数: 17532 | 7
Yes, there can be data members in interfaces. If the
interface is not
for constant definations only, there should be some methods
or semantic
features. In this case, the data members should be related
to the features
otherwise it does not make sense to put them there.
Considering following example, do you think it makes sense:
public interface MyConstants1 {
public static final int a = 1;
}
public interface MyConstants2 {
public static final int a = 2;
public static final int b = 3; |
|
