Re: What does the standard say?
From: Dan Pop (Dan.Pop_at_cern.ch)
Date: 03/31/04
- Next message: Dan Pop: "Re: What does the standard say?"
- Previous message: Dan Pop: "Re: #undef, #define"
- In reply to: Serve Laurijssen: "Re: What does the standard say?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 31 Mar 2004 13:25:17 GMT
In <lRuac.88$Y22.14394@zonnet-reader-1> "Serve Laurijssen" <cs@nospam.comp.com> writes:
>"Dan Pop" <Dan.Pop@cern.ch> wrote in message
>news:c4busv$ou3$2@sunnews.cern.ch...
>> >But we have been given tolower, toupper and islower, isupper.
>>
>> So that we can store our data in monocase, regardless of the user input,
>> if it's meant to be handled in a case insensitive manner. No need to
>> slow down the string comparison and string search functions for this
>> purpose.
>
>I don't think he was asking for strcmp and strstr to be case-insensitive,
>but more why there isn't a stristr and stricmp like many implementations
>have.
And I have explained that strstr and strcmp can do the job, where case
insensitiveness is desired, at no performance cost. Which means that
stristr and stricmp are both inefficient and superfluous.
Dan
-- Dan Pop DESY Zeuthen, RZ group Email: Dan.Pop@ifh.de
- Next message: Dan Pop: "Re: What does the standard say?"
- Previous message: Dan Pop: "Re: #undef, #define"
- In reply to: Serve Laurijssen: "Re: What does the standard say?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]