From: James Colannino <james@colannino.org>
To: eric@cisu.net
Cc: linux-c-programming@vger.kernel.org
Subject: Re: comparing char to other known char's
Date: Thu, 23 Jun 2005 22:48:20 -0700 [thread overview]
Message-ID: <42BB9EA4.1070906@colannino.org> (raw)
In-Reply-To: <200506232234.55312.eric@cisu.net>
Eric Bambach wrote:
>But maybe im being too pedantic ....your function DOES do the job ;)
>I just dont know how you plan to use it.
>
>
Well for my purposes it's probably ok. I'll be comparing very short
strings with it, although then again I'll be comparing a good number of
those short strings so the constant checking of those strings will still
add up. I do like your solution a lot, and actually I think I'll go
ahead and use it :)
James
P.S. Even though it's a small project that I'm working on, it is
something I plan on sharing with others, so as long as you wouldn't have
any objections I'd like to add a comment with your name to the code that
gives you credit for coming up with it.
--
My blog: http://www.crazydrclaw.com/
My homepage: http://james.colannino.org/
"A well regulated militia being necessary to the security of a free
state, THE RIGHT of the people to keep and bear arms SHALL NOT BE
INFRINGED." --United States Constitution, Second Ammendment
next prev parent reply other threads:[~2005-06-24 5:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 23:22 comparing char to other known char's James Colannino
2005-06-22 23:44 ` David L. Martin
2005-06-22 23:46 ` Eric Bambach
2005-06-23 0:25 ` James Colannino
2005-06-23 13:10 ` Adrian Popescu
2005-06-23 20:40 ` James Colannino
2005-06-23 22:57 ` Eric Bambach
2005-06-23 23:58 ` James Colannino
2005-06-24 0:25 ` James Colannino
2005-06-24 3:34 ` Eric Bambach
2005-06-24 5:48 ` James Colannino [this message]
2005-06-24 7:57 ` J.
2005-06-24 8:32 ` Glynn Clements
2005-06-25 11:58 ` HIToC
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42BB9EA4.1070906@colannino.org \
--to=james@colannino.org \
--cc=eric@cisu.net \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).