Comments for Ralph Schindler

Comment on Learning About Dependency Injection and PHP by sunshine1988

sunshine1988 — Mon, 26 Mar 2012 03:30:11 +0000

To retrieve the auto complete of IDE when you get Obj from DIC, just add a “@return …” comment.

/**
* Get some obj
* @return {the obj className or whatever it extends or implements}
*/
public function getSomeObj(){
//do something
return $someObj;
}
It works at least in ZendStudio and,I don’t test any other IDEs!
PS: sorry for my poor English~

Comment on PHP Constructor Best Practices And The Prototype Pattern by Niko Kivelä

Niko Kivelä — Thu, 22 Mar 2012 07:23:10 +0000

Against what @Ren said, I don’t think that __clone method should be considered “magic method” (even tho it is) in a way as __call or __set magic methods but in a way as __construct or __destruct. There’s a solid unambiguous point when objects __clone method is called, on keyword clone (compare to new keyword).

One point to notice, even tho you cannot overload clone method, you can “borrow” it from objects parent in a way you can call superclass’ constructor calling parent::__construct

Comment on PHP Constructor Best Practices And The Prototype Pattern by Mingomax

Mingomax — Wed, 21 Mar 2012 21:42:05 +0000

Ralph, hi from Brazil, your post its very nice and clarified certain dogmas that had on the use of some patterns and your article told me.

Excellent.

Tks.

Comment on Database Abstraction Layers Must Live! by Building layers on data access (Part 1)

Building layers on data access (Part 1) — Sat, 17 Mar 2012 08:54:24 +0000

[...] step to abstract data handling is to start using database abstraction, database abstraction must live. We’re not using code only to support different database vendors, but to ease the [...]

Comment on PHP Constructor Best Practices And The Prototype Pattern by John Congdon

John Congdon — Thu, 15 Mar 2012 12:35:25 +0000

I think Ralph is just sharing options. I appreciate seeing code in a new way. I like putting pieces of information like this into my toolbox, as it helps me think about all potential solutions and not just fall back to what I already know and use.

At the same time, having all of these useful comments has been great to also give me an insight into other opinions.

Thank you for the time to write this post and share.

Comment on PHP Constructor Best Practices And The Prototype Pattern by Greg

Greg — Tue, 13 Mar 2012 05:54:44 +0000

Ralph, very nice post. I’m always a little more a little more educated and in awe of your references.

This would be ideal for the Zend Paginator?

Maybe Off Topic, but is the Zend_Autoloader SOLID?

Comment on PHP Constructor Best Practices And The Prototype Pattern by Rob...

Rob... — Tue, 13 Mar 2012 05:52:53 +0000

Whilst I appreciate the benefits that the prototype pattern brings, like Ren, I’m not completely comfortable with objects that aren’t fully initialised after the constructor finishes. When I was cutting my teeth on C++ back in the days of Win16, this was called two-stage construction and was not considered a wise design decision. Maybe I’m just old fashioned and old habits die hard.

Regards,

Rob…

Comment on PHP Constructor Best Practices And The Prototype Pattern by Lukas

Lukas — Mon, 12 Mar 2012 14:39:54 +0000

@Gerard i assume you are partially complaining about PSR-0 here? the right solution is for APC to finally become hosted friendly and be bundled with PHP. but there are other solutions for shared host users without APC, including simply having a script that appends common classes into a single file that is loaded once.

as for your concern about lazy loading. most of the time if you need to lazy load a dependency, then probably you should move the logic to a different class anyway. classes with lots of optional dependencies are a code smell. additionally you can always still implement lazy creating of connections etc. once you are just creating objects without doing expensive stuff like opening files or remote connections, then you solved most of the issues from making instances of optional dependencies.

Comment on PHP Constructor Best Practices And The Prototype Pattern by Wojciech Soczyński

Wojciech Soczyński — Mon, 12 Mar 2012 12:19:25 +0000

@Giorgio – I agree with you, but in my opinion we don’t need multiple constructor signatures, as you said we can have static factory methods witch convert their arguments to fit the constructor. I think also, that in case when your object doesn’t need some fields initialized (in some usage contexts), you should create a separate class with a different constructor, rather than have constructors with different signatures.

Comment on PHP Constructor Best Practices And The Prototype Pattern by Gabriel

Gabriel — Mon, 12 Mar 2012 10:38:12 +0000

@Gerard: I think the issue of file access being expensive is somewhat mitigated when you’re using a Bytecode cache like APC (which you should do anyway).