I wasn't going to bother replying to you anymore, as I know other's feel this way also. But this last comment is flat out wrong, laughable at best.

"there are better ways, like using collections to store which class is edible for which class, etc."

You've obviously not coded in dotnet or java. As everyone has said, Interfaces are a great way to enforce good coding standards. I've not ever, ever seen a situation of spaghetti code arising out of use of interfaces.

The original start of the problem, the comment about simulating MI, obviously hit a spot with you. But you also obviously don't understand interfaces. They are a compromise over true MI. A problem with MI is method name collision. Won't happen with Interfaces.

But at the sametime, Interfaces allow for enforcing methods across separate processes.

Go ahead and post another assinine reply. Just don't expect any replies from me anymore.


>
>My code was obviously not the best, there are better ways, like using collections to store which class is edible for which class, etc.
>I did not want to argue about interfaces downsides. If you go back to my original message in this thread, my only comment was that "there is nothing wrong using interfaces to simulate MI" is debatable - mainly because of MI. In fact, I id not want to debate that either, there is enough debate out there from people a lot more qualified than me.