public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Pavel Machek <pavel@suse.cz>, Dave Jones <davej@suse.de>,
	kernel list <linux-kernel@vger.kernel.org>,
	vojtech@ucw.cz, andre@linuxdiskcert.org
Subject: Re: ide cleanup
Date: Fri, 08 Feb 2002 14:15:00 +0100	[thread overview]
Message-ID: <3C63CF54.9090308@evision-ventures.com> (raw)
In-Reply-To: <20020206205332.GA3217@elf.ucw.cz> <3C63C5EF.4050403@evision-ventures.com> <20020208133755.A10250@suse.cz>

Vojtech Pavlik wrote:

>On Fri, Feb 08, 2002 at 01:34:55PM +0100, Martin Dalecki wrote:
>
>>>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?


  reply	other threads:[~2002-02-08 13:15 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 [this message]
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
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=3C63CF54.9090308@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=andre@linuxdiskcert.org \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=vojtech@suse.cz \
    --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