From: <pkoning@equallogic.com>
To: <jimb@codesourcery.com>, <mark.kettenis@xs4all.nl>
Cc: <drow@false.org>, <eliz@gnu.org>, <dewar@adacore.com>,
<nickrob@snap.net.nz>, <jan.kratochvil@redhat.com>,
<Mathieu.Lacage@sophia.inria.fr>, <gdb@sourceware.org>
Subject: RE: [RFC] Signed/unsigned character arrays are not strings
Date: Wed, 28 Feb 2007 13:05:00 -0000 [thread overview]
Message-ID: <86A3089001A44141B76B882059E7E53B01CCEED7@M31.equallogic.com> (raw)
> Okay, here's a horrible idea. :) With this patch:
>
> $ cat chars.c
> #include <stdio.h>
> #include <stdint.h>
>
> typedef char byte_t;
>
> char *c = "chars";
> unsigned char *uc = "unsigned chars";
> signed char *sc = "signed chars";
> byte_t *b = "bytes";
> int8_t *i8 = "int8_t's";
> uint8_t *ui8 = "uint8_t's";
Neat.
I would tweak it a little. People might be using typedefs
for character strings that wrap, say, "unsigned char".
So if you're going to do a heuristic on the name, treat
it as a character string if the name ends in "char" (not
necessarily with a preceding space) or "char_t" (because
many people use _t as the suffix for typedef names).
paul
next reply other threads:[~2007-02-28 1:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 13:05 pkoning [this message]
2007-03-01 11:01 ` Mark Kettenis
-- strict thread matches above, loose matches on Subject: below --
2007-02-24 16:13 Nick Roberts
2007-02-24 20:11 ` Daniel Jacobowitz
2007-02-24 20:53 ` Nick Roberts
2007-02-24 21:07 ` Jan Kratochvil
2007-02-25 8:00 ` Daniel Jacobowitz
2007-02-25 19:54 ` Nick Roberts
2007-02-25 21:07 ` mathieu lacage
2007-02-26 0:45 ` Jan Kratochvil
2007-02-27 7:17 ` Eli Zaretskii
2007-02-27 9:29 ` Daniel Jacobowitz
2007-02-27 12:02 ` Nick Roberts
2007-02-27 17:06 ` Robert Dewar
2007-02-27 18:42 ` Daniel Jacobowitz
2007-02-27 21:53 ` Eli Zaretskii
2007-02-27 22:12 ` Daniel Jacobowitz
2007-02-27 22:14 ` Mark Kettenis
2007-02-28 0:47 ` Paul Koning
2007-02-28 1:14 ` Jim Blandy
2007-02-28 1:59 ` Jim Blandy
2007-02-28 5:26 ` Nick Roberts
2007-02-28 14:35 ` Daniel Jacobowitz
2007-03-01 0:43 ` Jim Blandy
2007-03-01 0:54 ` Nick Roberts
2007-02-27 21:47 ` Eli Zaretskii
2007-02-27 22:12 ` Daniel Jacobowitz
2007-04-10 21:59 ` Daniel Jacobowitz
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=86A3089001A44141B76B882059E7E53B01CCEED7@M31.equallogic.com \
--to=pkoning@equallogic.com \
--cc=Mathieu.Lacage@sophia.inria.fr \
--cc=dewar@adacore.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=jimb@codesourcery.com \
--cc=mark.kettenis@xs4all.nl \
--cc=nickrob@snap.net.nz \
/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