NYCPHP Meetup

[Adam Fields]

On Wed, Oct 16, 2002 at 07:52:21PM -0400, Jim Hendricks wrote:
> Yeah, your right.  Sometimes though encapsulation can be a bad thing 
> though when it hides too much and you have to pull your hair out later 
> trying to figure out what the heck you did.  There's still too much 
> procedural coding in my blood that avoids OOP unless I have to ( as is 
> the case with Java ).  In the case of Java and C++, I preceive that the 
> performance of the VM/runtime would be better if you were to drop the 
> OOP and just go with good old procedural code.  Granted procedural code 
> can be messy, but an experienced coder should be able to write modular 
> proc code to rival OOP.  Just my own old fart ( 19 years in the business 
> I guess qualifies for old fartism in the IT world even though I'm only 
> 37 ) biased opinion probably not worth admitting!

I've been concentrating recently on building reusable components and
frameworks. While this is doable with procedural code, having object
handling makes some of it much easier. In PHP, the lack of private and
protected entities makes this more a syntactical issue than true
encapsulation.

I do, however, find that even the illusion of encapsulation tends to
encourage better code organization.

-- 
				- Adam

-----
Adam Fields, Managing Partner, fields at surgam.net
Surgam, Inc. is a technology consulting firm with strong background in
delivering scalable and robust enterprise web and IT applications.
http://www.adamfields.com