Re: What design patterns do you usually use?
| From: | Daniel Brown | Date: | Wed, 27 Feb 2008 16:57:53 +0000 |
| Subject: | Re: What design patterns do you usually use? | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-270329@lists.php.net to get a copy of this message | ||
On Wed, Feb 27, 2008 at 11:53 AM, Jason Pruim <japruim@raoset.com> wrote:
>
> On Feb 27, 2008, at 11:42 AM, Aschwin Wesselius wrote:
> >
> > No. Give me procedural code please. I can read that from top to
> > bottom, it sticks on 1 flow of the processing. Downside is having
> > some code multiple times all over the place (hence an argument for
> > OOP).
>
> Wouldn't that be a perfect place for functions though? Write the
> actual code just once and then call it throughout... At least that
> way, it (should be) easy enough to track down the actual code that
> needs to be changed... Assuming of course that the original programmer
> organized the functions either into separate files, or did 1 big file
> of functions...
Or the functions are in the same file as the rest of the code. Or
you trace the includes/requires. Or there is stack tracing on
__FILE__....
--
</Dan>
Daniel P. Brown
Senior Unix Geek
<? while(1) { $me = $mind--; sleep(86400); } ?>