What is idiosyncratic interface ?
P.S. Sorry, I don't want to google it...
On Tue, Jun 21, 2011 at 11:08 AM, IO niezus...@googlemail.com wrote:
Hi, in Wicket there are many idiosyncratic interfaces, such as IModel T. I
often see that these interfaces are implemented several times in a project.
Not sure what you're getting at. IModel is sort of hungarian notation:
Interface for Model. Not idiosyncratic. Read the definition of
Idiosyncratic Interfaces:
If a general interface is implemented by only one class (whose
implementation may be modified over time, but with no two alternatives
Am 21.06.2011 10:08, schrieb IO:
Hi, in Wicket there are many idiosyncratic interfaces, such as IModelT. I
often see that these interfaces are implemented several times in a project.
An idiosyncratic interface should be implemented only once in a project. Can
someone explain that to me?
IO.
--
I have expressed myself wrong. In the interface-based programming, general
interfaces are classified into family interfaces and idiosyncratic
interfaces. I looked up again and noticed that the word idiosyncratic is
used only in Germany. Can anyone else tell me what the I stands for the
interfaces?
Ok thank you. That has answered my question.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/idiosyncratic-interfaces-such-as-IModel-IVisitor-tp3613440p3613492.html
Sent from the Users forum mailing list archive at Nabble.com.
An interface is a piece of code one writes when they are too lazy to think of
the implementation.
An abstract Class is one where you have no idea how the hell you will
complete the rest!
An idiosyncratic interface is 1 to 1 relation with your class because the
programmer did not have the guts to
