Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:10752
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <40DAB758.1020709@velum.net>
Date: Thu, 24 Jun 2004 07:13:28 -0400
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
MIME-Version: 1.0
To: Taco Van Den Broek <taco@procurios.nl>
CC:  internals@lists.php.net
References: <40DA29C3.1090301@velum.net> <20040624074757.1883.qmail@pb1.pair.com>
In-Reply-To: <20040624074757.1883.qmail@pb1.pair.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: static/object method
From: hans@velum.net (Hans Lellelid)

Taco Van Den Broek wrote:

 > Hans Lellelid wrote:
 >> static, default behavior, probably accounts for 80% of uses:
 >>
 >> $c = new Criteria(Author::NAME, "Leo");
 >> $a = AuthorFinder::find($c);
 >
 >
 > You pass your criteria to your search class as instantiated objects, why
 > don't you pass your parameters/config flags as another type of object?
 > Maybe like this:
 >
 > $c = new Criteria(Author::NAME, "Leo");
 > $f = new ConfigFlag(AuthorFinder::LIMIT, '5');
 > $a = AuthorFinder::find($c, $f);
 >
 > You could then check the $f object for any customizations, just like you
 > check the $c object for where to search.

That's a good suggestion -- probably the cleanest design possible in 
current PHP object model.

Thanks,
Hans