On Sat, 15 Dec 2001 06:17, Lucas Gonze wrote:
> > Declaring access modifiers on the interface goes against the
> > recomendation of the JLS and should have zero effect on the code. Which
> > compiler is not producing such results?
>
> There's no compiler fault involved, Pete. In this case coders will receive
> a slightly baffling compile time error message with regard to changing
> access privileges in an implementing class, which slows down the work of
> creating a Mailet.
Still have no idea what you are talking about. If you have
interface Foo
{
void bar();
}
class FooImpl implements Foo
{
public void bar() {}
}
You should not get any warning whatsoever. As a matter of fact good compilers
will actually issue warnings if you put a public access specifier in the
interface. If you are not seeing this behaviour then your tools are horribly
broken and not spec compliant.
If you just want public in front of it so you can copy paste then you have
zero sympathy from me but if there is a real reason then share it.
--
Cheers,
Pete
-------------------------------------------------------------
| Egoism is the drug that soothes the pain of stupidity. |
-------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
