Should I put an @Override tag if I implement an interface method? I know that the @Override tag should be there when you override the superclass method (and not the interface). But what about implementing an interface method?
Well yes :
You should use @Override whenever possible. This prevents simple manufacturing errors. Example:@Override public boolean equals(MyObject mObj){ // code ... } This does not compile because it incorrectly overrides the values.The same goes for methods that implement the interface (1.6 and above) only) or override the class of the superclass Method.
You should use @Override whenever possible. This prevents simple manufacturing errors. Example:
@Override public boolean equals(MyObject mObj){ // code ... }
This does not compile because it incorrectly overrides the values.
The same goes for methods that implement the interface (1.6 and above) only) or override the class of the superclass Method.
Source: https://habr.com/ru/post/1768162/More articles:Draw part of image in CGBitmapContext - cocoadoctrine of findby magic null value - phpAlgorithm for fast point search and line of sight - algorithmCan I deploy a .NET 4 client profile through ClickOnce for non-administrators? - .netReset submit button not working using MVC 2 - formsRuby on Rails OAuth application runs on the client, but not on the server (OAuth :: Unauthorized (401 Unauthorized)) - authenticationGame File File Format - c ++JQuery: how to release all event handlers, dom changes? - jqueryThe shutter closes when executing a bash script - bashHas anyone here tried PHP On Pie? - phpAll Articles