From: "J." <mailing-lists@xs4all.nl>
To: linux-c-programming@vger.kernel.org
Subject: Re: comparing char to other known char's
Date: Fri, 24 Jun 2005 09:57:19 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0506240936200.565-100000@hestia> (raw)
In-Reply-To: <42BB52E4.5090504@colannino.org>
On Thu, 23 Jun 2005, James Colannino wrote:
> Eric Bambach wrote:
>
> > 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.
>
> Here's what I've whipped up based on your suggestion that I should look
> for legal characters instead of the other way around:
>
> <CODE>
>
> /* This function returns 1 if the character being checked is legal and 0
> if it isn't. */
>
> int legal_characters(char character_to_check) {
>
> int index;
> legal_characters[] =
> "abcdefghijklmnopqrstuvwxyzAVCDEFGHIJKLMNOPQRSTUVWXYZ1234567890_-";
I'm not going to repeat all the answers you already had, but you know the
#include <ctype.h> ?
The above [abcdef... ABC. etc..] `man ascii' e.g.
uppercase alpha (c >= 65 && c <= 90) ,
lowercase alpha (c >= 97 && c <= 122),
numerals ... (c >= 48 && c <= 57) etc..
or with ctype.h ... isdigit(), isalnum() .....
#include <stdio.h>
#include <ctype.h>
int legal_characters(char ch) {
register int retv = -1;
if(isalpha(ch) || isdigit(ch) || ch == '-' || ch == '_')
retv = 1;
else
retv = 0;
return retv;
}
int main(void) {
char c;
while((c = getchar()) != EOF) {
if(legal_characters(c))
putchar(c);
}
return 0;
}
You could also use the ctype macro's grouped together in your own defined
macro..
Maybe it's good to point out that the users of your program can also
be chinese users and other `foreign' users that use different character
sets that do not fit into the 1 byte character..
Cheers..
J.
> int number_of_legal_chars = sizeof(legal_characters) / sizeof(char);
>
> for (index = 0; index < number_of_legal_chars; ++index) {
> if (character_to_check == legal_characters[index])
> return 1;
> }
>
> return 0;
>
> </CODE>
next prev parent reply other threads:[~2005-06-24 7: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
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. [this message]
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=Pine.LNX.4.21.0506240936200.565-100000@hestia \
--to=mailing-lists@xs4all.nl \
--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).