@kirk >> Properties are a 1-to-1 relationship of a classes member and the state >> it's representing, > which is a violation of encapsulation and promotes unnecessary couplings.
That 1-to-1 relationship is the encapsulation, and it's actually promoting the point. >> To properly get closures, you need function pointers, and that's why >> we need them in Java, and with function pointers we can implement >> proper events fairly easily. > You need to make methods first class citizens and then you can implement > closures properly. Exposing pointer is something we want to avoid IMHO. To the casual C# programmer they wouldn't even know they were actually using function pointers. The language takes care of >> since >> stateless code can't really listen to events in the first place. >> > Why not? Well you can, but more so why would you? Events are more suited to something that is going to hang around for a while in a state-full fashion. -Brett --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
