dhol68 wrote:
>
>
> Hi,
>
> having the default impl in the abstract class will be in my opinion
> confusing for the user, because he will not see what operations should be
> implemented only if he looks at the abstract class
>
>
I'm not shure about that. If this behavior is well documented, I see no
problem.
> ......by default he should
> only open/work with the base class in my understanding.
>
thats absolutly true ! :-)
> And what happens if
> somebody extends the generated abstract class manually and all the methods
> have def impl already?
>
Overwrite the methods.
Ok, in this case you must do this manually, and cant make it your ide ;-)
Another little note: If you write the default implementation into the
manual-base class,
new operations may not be generated, because the generator don't overwrite
the existing class (because of the manuall outlet).
Regards
Darius
--
View this message in context:
http://www.nabble.com/-Cartridges%3A-JavaBasic--Should-methods-definded-in-an-Interface-be-abstract-in-the-AbstractClass--tf3768454s17564.html#a10680216
Sent from the Fornax-Platform mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Fornax-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fornax-developer
