tag:blogger.com,1999:blog-10748614.post111561297988539933..comments2024-02-28T12:34:09.691-05:00Comments on FrazzledDad: Hansleman's List: Aspect/Interface/Object -Oriented ProgrammingJim Holmeshttp://www.blogger.com/profile/05869146736565695900noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-10748614.post-1121566431082311942005-07-16T22:13:00.000-04:002005-07-16T22:13:00.000-04:00You're welcome, Paul. I don't know that I did tha...You're welcome, Paul. I don't know that I did that great a job explaining these, but I gave it a shot.<BR/><BR/>The article I liked to did a fair job explaining AOP -- but it took me several re-reads to start to getting a feel for what was going on. The paint example I mentioned from that article seemed to make good sense.<BR/><BR/>Interface vs. Object programming takes a bit of noodling out, too. I'm not sure I can come up with a clearer explanation that interface programming's really like having a contract between two sides, and either side really doesn't know or care about the other.<BR/><BR/>If you have access to it, take a look at Bill Wagner's <I>Effective C#</I>. He's got a very good blurb in there on using interfaces.Jim Holmeshttps://www.blogger.com/profile/05869146736565695900noreply@blogger.comtag:blogger.com,1999:blog-10748614.post-1121534903331484852005-07-16T13:28:00.000-04:002005-07-16T13:28:00.000-04:00Thanks, Jim, for at least trying to answer a very ...Thanks, Jim, for at least trying to answer a very complex question! AOP has me entirely lost, and as for the difference between Interface and OOP, I still cant see it. Your attempt, however (the first I've read) is very much appreciated.Anonymoushttps://www.blogger.com/profile/18207763322691376601noreply@blogger.com