From: Eric Bambach <eric@cisu.net>
To: James Colannino <james@colannino.org>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: comparing char to other known char's
Date: Thu, 23 Jun 2005 17:57:58 -0500 [thread overview]
Message-ID: <200506231757.58518.eric@cisu.net> (raw)
In-Reply-To: <42BB1E25.1050500@colannino.org>
On Thursday 23 June 2005 03:40 pm, James Colannino wrote:
> Adrian Popescu wrote:
> > On Thursday 23 June 2005 02:22, James Colannino wrote:
> >>Hey everyone. I hope this isn't a stupid question. I've been googling
> >>around trying to find a function that I can use but haven't been
> >>successful. Here's what I want to be able to do:
> >>
> >>let's say I have a char called 'character.' I want to compare
> >>'character' to see if it's any one of the characters in a list. For
> >>example, maybe I would want to test character to see if it's either 'e',
> >>'r', '*', etc.
> >>
> >>Is this easy enough to implement? I could do if (character == 'e' ||
> >>character == [...] and so on and so forth, but this seems much to
> >>tedious and unreadable to be my only solution. If anyone has any ideas
> >>I'd be extremely grateful :) Thanks very much in advance.
> >>
> >>James
> >
> > the way you put it ( if (character == 'e' || ....) ; it is TRUE if
> > any (or only one) from those chars exists ;
>
> I know. That's what I wanted. Basically, I want to check to see if
> each character in a string matches any one of an illegal set of
> characters. Thus, the function would fail if it encountered an illegal
> character in the string.
>
> James
Generally speaking (in terms of input validation), its better practice to
check against a LEGAL set of characters rather than an illegal set. That way
you can get all the characters you need, but everything else is blocked. If
you block illegal ones you're bound to miss a few or even ones from extended
charsets and input methods that you might not have thought of that could
wreck havoc in your program.
HTH!
--
----------------------------------------
--EB
> All is fine except that I can reliably "oops" it simply by trying to read
> from /proc/apm (e.g. cat /proc/apm).
> oops output and ksymoops-2.3.4 output is attached.
> Is there anything else I can contribute?
The latitude and longtitude of the bios writers current position, and
a ballistic missile.
--Alan Cox LKML-December 08,2000
----------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-06-23 22:57 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 [this message]
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
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=200506231757.58518.eric@cisu.net \
--to=eric@cisu.net \
--cc=james@colannino.org \
--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).