From: James Antill <james@and.org>
To: wichert@cistron.nl (Wichert Akkerman)
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide cleanup
Date: 08 Feb 2002 18:00:22 -0500 [thread overview]
Message-ID: <nnit97a8ah.fsf@code.and.org> (raw)
In-Reply-To: <20020206205332.GA3217@elf.ucw.cz> <3C63C5EF.4050403@evision-ventures.com> <20020208133755.A10250@suse.cz> <3C63CF54.9090308@evision-ventures.com> <a40okb$mds$1@picard.cistron.nl>
In-Reply-To: <a40okb$mds$1@picard.cistron.nl>
wichert@cistron.nl (Wichert Akkerman) writes:
> In article <3C63CF54.9090308@evision-ventures.com>,
> Martin Dalecki <dalecki@evision-ventures.com> wrote:
> >The _t at the end of type names is a POSIX habit of markup for system
> >defined types - this should *NOT* be used in user land programms but is OK for
> >the kernel.
>
> Why, I don't see that. Everyone should use whatever notation he/she
> feels most comfortable with.
Err, what?
Sure mindless programmers can call a function strnew() or strconcat()
if they "feel most comfortable" with that. But it's _wrong_, as that's
a reserved namespace of ISO C. Jut as *_t is a reserved namespace of
POSIX.
Opengroup seems really slow atm., but hopefully you'll believe one of...
http://sources.redhat.com/ml/libc-alpha/2000-09/msg00185.html
http://www.ioccc.org/1998/data
--
# James Antill -- james@and.org
:0:
* ^From: .*james@and\.org
/dev/null
next prev parent reply other threads:[~2002-02-08 23:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 20:53 ide cleanup Pavel Machek
2002-02-07 3:34 ` Andre Hedrick
2002-02-07 7:29 ` Vojtech Pavlik
2002-02-07 12:40 ` Pavel Machek
2002-02-08 12:34 ` Martin Dalecki
2002-02-08 12:37 ` Vojtech Pavlik
2002-02-08 13:15 ` Martin Dalecki
2002-02-08 14:50 ` Wichert Akkerman
2002-02-08 15:08 ` Dave Jones
2002-02-08 15:09 ` Wichert Akkerman
2002-02-08 15:08 ` Martin Dalecki
2002-02-08 23:00 ` James Antill [this message]
2002-02-08 22:10 ` Pavel Machek
2002-02-09 18:19 ` Bill Davidsen
2002-02-09 18:35 ` Vojtech Pavlik
2002-02-11 19:15 ` Bill Davidsen
2002-02-12 10:00 ` Pavel Machek
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=nnit97a8ah.fsf@code.and.org \
--to=james@and.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wichert@cistron.nl \
/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