Re: [PHP4BETA] New function chrcount
| From: | John Steele | Date: | Mon, 24 Apr 2000 15:11:17 +0000 |
| Subject: | Re: [PHP4BETA] New function chrcount | ||
| References: | 1 2 3 4 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-14029@lists.php.net to get a copy of this message | ||
Hey everyone,
I'm already subscribed to the list. Please stop CC'ing my address :)
I like the idea of it beginning with str_, so taking's Andi's example, how about
str_num_matches(), or str_num_occurs().
At 4/25/2000 12:52 AM, you wrote:
>At 04:45 PM 4/24/00 -0500, Andrei Zmievski wrote:
>>On Mon, 24 Apr 2000, Colin Viebrock wrote:
>> > How about num_times_char_is_in_string()? :)
>> >
>> > I'm still rooting for str_chr_freq(), or even just chr_freq(). I realize
>> > that etyomologists may cringe at the inexact use of "frequency", but
>> > "char_occurence" and "char_tally" look or sound funny, and and
>> > agree
>> > with Andi that "*_count" is kina ambiguous.
>> >
>> > How about str_matches() or chr_matches() ?
>>
>>Well, this is ambiguous too. Is "matches" a noun or a verb here?
>
>What is ambiguous is str_count(). It barely gives you a clue of what the
>function does.
>num_str_matches() might be more appropriate. Don't save a few characters
>just because you want to type less, it is more important that you find a
>name which makes sense and that the function's behavior can more or less be
>understood by its name.
>
>Andi
>---
>Andi Gutmans <andi@zend.com>
>http://www.zend.com/
--
/* SteeleSoft Consulting John Steele - Systems Analyst/Programmer
* We also walk dogs... jsteele@writeme.com
* http://www.gamecomputer.com/ssc/
*/