Re: Constructor as a "Reset" Button
- From: Sanders Kaufman <bucky@xxxxxxxxxxx>
- Date: Wed, 25 Jul 2007 14:17:02 -0500
Michael Fesser wrote:
.oO(Sanders Kaufman)
But a core design principle is to not use resources unnecessarily - so calling TWO functions each time an object is created would violate that principle.
Are you kidding or trolling? Why are you calling multiple methods, if
all could be done in a single one? Why do you use OOP at all? Or PHP?
Why not directly write pure Assembler code?
Because that would violate a core design principle - that the app be written in PHP4.
_Every_ step taken to a higher, more abstract level "wastes" sooo many
resources - millions of CPU cycles just in order to load, parse and
compile your class file, so you can use it! And you're worried about the
time taken for a _single_ method call? Sorry, but that's just absurd.
Yeah - but I recycle my plastic and glass, too. I don't see where it's made my neighborhood any tidier, but it's the principle of the thing.
.
- References:
- Re: Constructor as a "Reset" Button
- From: Sanders Kaufman
- Re: Constructor as a "Reset" Button
- From: ZeldorBlat
- Re: Constructor as a "Reset" Button
- From: Sanders Kaufman
- Re: Constructor as a "Reset" Button
- From: Jerry Stuckle
- Re: Constructor as a "Reset" Button
- From: Sanders Kaufman
- Re: Constructor as a "Reset" Button
- From: ZeldorBlat
- Re: Constructor as a "Reset" Button
- From: Sanders Kaufman
- Re: Constructor as a "Reset" Button
- From: Toby A Inkster
- Re: Constructor as a "Reset" Button
- From: Sanders Kaufman
- Re: Constructor as a "Reset" Button
- From: Michael Fesser
- Re: Constructor as a "Reset" Button
- Prev by Date: Re: Constructor as a "Reset" Button
- Next by Date: Re: Constructor as a "Reset" Button
- Previous by thread: Re: Constructor as a "Reset" Button
- Next by thread: Re: Constructor as a "Reset" Button
- Index(es):
Relevant Pages
|