From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Nigel Cunningham <ncunningham@users.sourceforge.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@digeo.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: PATCH 1/2: Make gotoxy & siblings use unsigned variables
Date: Fri, 9 Jan 2004 14:22:12 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0401091415430.571@chaos> (raw)
In-Reply-To: <1073672901.2069.15.camel@laptop-linux>
On Sat, 10 Jan 2004, Nigel Cunningham wrote:
> This patch makes console X and Y coordinates unsigned, rather than
> signed. Issues with wide (> 128 char?) consoles, seen when developing
> Software Suspend's 'nice display' are thus fixed. A brief examination of
> related code showed that this use of signed variables was the exception
> rather than the rule.
>
> Regards,
>
> Nigel
[SNIPPED...]
Question: Shouldn't we be using "size_t" for unsigned int, and
"ssize_t" for signed? If the "ints" are going to be changed,
they probably should be changed only once. As I recall, size_t
was the largest unsigned int that would fit into a register and
ssize_t was the largest signed int that would fit.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-01-09 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 18:33 Nigel Cunningham
2004-01-09 19:22 ` Richard B. Johnson [this message]
2004-01-09 19:43 ` Nigel Cunningham
2004-01-09 20:33 ` Andries Brouwer
2004-01-09 21:26 ` Nigel Cunningham
2004-01-10 3:34 ` Edgar Toernig
2004-01-13 21:57 ` Pavel Machek
2004-01-09 21:32 ` Andrew Morton
2004-01-09 21:38 ` Andrew Morton
[not found] <1c9S3-75-23@gated-at.bofh.it>
[not found] ` <1cauN-131-17@gated-at.bofh.it>
[not found] ` <1cb7n-1Z6-17@gated-at.bofh.it>
[not found] ` <1cbAw-2BB-27@gated-at.bofh.it>
2004-01-16 18:41 ` Bill Davidsen
2004-01-16 18:54 ` Nigel Cunningham
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.53.0401091415430.571@chaos \
--to=root@chaos.analogic.com \
--cc=akpm@digeo.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@users.sourceforge.net \
/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®