[comp.lang.c] The reason behind the strcmp

afoiani@nmsu.edu (Anthony Foiani) (10/17/90)

I seem to remember that the original poster was looking for a 'quick'
way to speed up code with lots of 'strcmp()'s in it.  

And so the deluge began... fourty days and nights of various strcmp
code and commentary...

...tony
--
Tony Foiani  a.k.a. Tkil  (mcsajf@nmsuvm1.bitnet) or (afoiani@nmsu.edu)
Supporting:  Unix / DOS / VMS / Macintosh / "What's this?" / Apple II

cdm@gem-hy.Berkeley.EDU (Dale Cook) (10/20/90)

In article <AFOIANI.90Oct16195905@dante.nmsu.edu>, afoiani@nmsu.edu
(Anthony Foiani) writes:
|> I seem to remember that the original poster was looking for a 'quick'
|> way to speed up code with lots of 'strcmp()'s in it.  
|> 
|> And so the deluge began... fourty days and nights of various strcmp
|> code and commentary...
|> 
|> ...tony
|> --
|> Tony Foiani  a.k.a. Tkil  (mcsajf@nmsuvm1.bitnet) or (afoiani@nmsu.edu)
|> Supporting:  Unix / DOS / VMS / Macintosh / "What's this?" / Apple II

For your reading pleasure, here is the original article.  I don't see where
the author asked for "a quick way to speed up code with lots of strcmp()'s
in it".  In fact, I don't see where he referred to "strcmp()" at all.  
Perhaps I missed something...

Article 6403 of comp.lang.c

Hello...

	I'm sorry if this is a trival task, but I would like a function that
compares two strings.  I would like to be able to find if a string is equal to,
less than, or greater than another string.  I tried writing a routinue myself,
but I just can't seem to do it, so I thought I'd ask.

	I wouldn't mind some code, or just the basic algorithm maybe.

	If anyone can help me, please email or post...

Thanks.

Bernard.

-------------

---Dale

Neither the United States Government nor the Idaho National
Engineering Laboratory nor any of their employees, makes any warranty,
expressed or implied, or assumes any legal liability or responsibility
for the accuracy, completeness, or usefulness of any information,
product, or process disclosed, or represents that its use would not
infringe privately owned rights.  Reference herein to any specific
commercial products, process, or service by trade name, trademark
manufacturer, or otherwise, does not necessarily constitute or imply
its endorsement, recommendation, or favoring by the United States
Government or the Idaho National Engineering Laboratory.  The views and
opinions of authors expressed herein do not necessarily state or reflect
those of the United States Government nor the Idaho National Engineering
Laboratory, and shall not be used for advertising or product endorsement
purposes.