It is my understanding that the bulk of those OOP design patterns are useful to get around the limitations of static languages like C++ and Java, that don't allow you to arbitrarily add/remove properties from instances, change the type of a value, or allow higher order functions (functions that return functions values), or allow you to pass in functions as values. Given that javascript allows all those things, much of those traditional OOP design patterns don't make much sense, because they're getting around a limitation that doesn't exist.
I haven't extensively used the OOP facilities in PHP, I've always found the syntax to be ugly as hell, I could never bring myself to type that crap willingly. So unfortunately, I cannot speak knowledgably about how difficult or hard it is in PHP. On Tue, Oct 28, 2008 at 1:17 AM, James Jeffery <[EMAIL PROTECTED]> wrote: > My statement was not worded correctly. > > I use Java, C++, PHP and Javascript and I can tell you that out of the lot > of them, Javascript is the most difficult to incorperate conventional Object > Orientated design. For example you cannot simply define classes, or use > visability keywords (you can do it, but not the conventional way) and some > of the OOP design patterns are difficult to put into Javascript. > > I have the Apress book on Javascript Design Patterns, which helped alot when > learning OOP in JS. > > Sorry my wording was wrong. I think the above is what I meant. > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
