> Why isn't it declared public like in my implementing class ?
Because in a interface you need not to define any visibility; it's
automatically public. If you have the extra "public", I think, Jikes
will show a warning message, that it is useless.
Tom
On Fri, 12 Jul 2002 11:48:14 +0200, "Guillaume Laforge"
<[EMAIL PROTECTED]> wrote:
> Hello everybody,
>
> Well, it's maybe not actually a bug, but I was playing with "pull member up"
> refactoring. It's just really great.
> But I have a question about it and was wondering whether it was a bug, or
> just simply a misunderstanding from me.
>
> I have an interface, and I have a class that implements this interface.
> I created a new method in my class, and then decided to pull this new method
> up inside the interface.
> So I had the following method :
>
> public String[] getWords()
> {
> return (String[])commonWords.toArray(new String[commonWords.size()]);
> }
>
> I refactored it with "pull member up". And I got that in my interface :
>
> String[] getWords();
>
> Why isn't it declared public like in my implementing class ?
> Is a bug ? I wonder why the visibility is not the same.
>
> Guillaume
>
>
_______________________________________________
Eap-bugs mailing list
[EMAIL PROTECTED]
http://lists.jetbrains.com/mailman/listinfo/eap-bugs
