tag:blogger.com,1999:blog-5721355636181981292.comments2009-05-17T01:03:16.196+02:00dispel magiceliashttp://www.blogger.com/profile/03352023807135754785noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5721355636181981292.post-9133604753544170452009-05-17T01:03:00.000+02:002009-05-17T01:03:00.000+02:00Amazing, just found this post. Yes, that wasn't th...Amazing, just found this post. Yes, that wasn't the best piece of code I have ever written. That's what you get for coding at 3am. Simplicity is very different now that it was when you last looked at it. Would be interested to hear your thoughts. <br /><br />http://www.simplicityphp.com<br /><br />Cheers<br /><br />JohnAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5721355636181981292.post-5722877043522416742008-03-14T16:24:00.000+01:002008-03-14T16:24:00.000+01:00Hi Jonathan,thanks for your response! My suggestio...Hi Jonathan,<BR/>thanks for your response! My suggestion is to stick to native array's as long as possible. You can solve anything without a collection-like-something. Testability and readability are reasons for me to bring a specialized array object into the game. I like all the SPL stuff, but ie ArrayAccess has to many drawbacks to adapt it on a broad range. It's just not fool proof. Further i don't want to learn another API. I know how array_merge() etc. works and i have easy access to the php documentation. But an array object may have an equivalent called $o->join() (and not merge) with a slight different implementation. I have to learn a new interface for problems that i already know how to solve.<BR/><BR/>Why take so many drawbacks and dispel one of the great powers of php?<BR/><BR/>e.eliashttps://www.blogger.com/profile/03352023807135754785noreply@blogger.comtag:blogger.com,1999:blog-5721355636181981292.post-2346390126648442062008-03-08T17:01:00.000+01:002008-03-08T17:01:00.000+01:00Hi, Elias. I'm Double Compile, the project lead f...Hi, Elias. I'm Double Compile, the project lead for Xyster.<BR/><BR/>I'm glad you took the time to check out the framework enough that you can give us some feedback. I understand your frustration with the Java concept of collections. I don't think ours is <I>exactly</I> in that vein, but it's close.<BR/><BR/>We really needed collection objects that hooked into PHP's SPL interfaces. Several things in the framework needed strongly-typed sets and sortable entries. <BR/><BR/>How would you do it differently? Can you think of any suggestions? You can e-mail me if you'd like.<BR/><BR/>Thanks!<BR/>-DCAnonymoushttps://www.blogger.com/profile/12580149030163005166noreply@blogger.com