From: Pavel Machek <pavel@suse.cz>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
vojtech@ucw.cz, andre@linuxdiskcert.org
Subject: Re: ide cleanup
Date: Fri, 8 Feb 2002 23:10:17 +0100 [thread overview]
Message-ID: <20020208221016.GB988@elf.ucw.cz> (raw)
In-Reply-To: <20020206205332.GA3217@elf.ucw.cz> <3C63C5EF.4050403@evision-ventures.com> <20020208133755.A10250@suse.cz> <3C63CF54.9090308@evision-ventures.com>
In-Reply-To: <3C63CF54.9090308@evision-ventures.com>
Hi!
> >>>IDE is
> >>>* infested with polish notation
> >>>
> >>I don't see any polish notation there. Could you please explain what you
> >>mean with this note?
> >>
> >
> >I think Pavel meant what I think is called "hungarian notation", adding
> >_t's to type identifiers or adding _i or i_ to integer variables.
> >
> The encoding of type signatures in function names is indeed called
> hungarian notation.
> 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. However for the
> ide drivers it's indeed unnecessary
> code noise.
>
> Polish notation is the anglo-saxon term for a mathematical expression
> syntax which is avoiding
> parents by not using an "in between" operator notation but using
> functional notation instead.
> It was invented by ?ukasiewich at the beginning of the last century for
> formal logic and is indeed more
> convenient there if you start to deal with long expressions.... Just to
> clarify the terms OK?
Sorry, I really meant that nasty _t. (The driver even did things like
struct foo xyzzy;
memset(&xyzzy, 0, sizeof(foo_t));
using both 'struct foo' and foo_t for one variable.
Pavel
--
(about SSSCA) "I don't say this lightly. However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
next prev parent reply other threads:[~2002-02-09 18:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 20:53 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
2002-02-08 22:10 ` Pavel Machek [this message]
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=20020208221016.GB988@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=andre@linuxdiskcert.org \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@ucw.cz \
/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
all inboxes | Powered by JetHome®