Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263850AbUAITWd (ORCPT ); Fri, 9 Jan 2004 14:22:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263930AbUAITWd (ORCPT ); Fri, 9 Jan 2004 14:22:33 -0500 Received: from chaos.analogic.com ([204.178.40.224]:3200 "EHLO chaos.analogic.com") by vger.kernel.org with ESMTP id S263850AbUAITWc (ORCPT ); Fri, 9 Jan 2004 14:22:32 -0500 Date: Fri, 9 Jan 2004 14:22:12 -0500 (EST) From: "Richard B. Johnson" X-X-Sender: root@chaos Reply-To: root@chaos.analogic.com To: Nigel Cunningham cc: Linux Kernel Mailing List , Andrew Morton , Benjamin Herrenschmidt Subject: Re: PATCH 1/2: Make gotoxy & siblings use unsigned variables In-Reply-To: <1073672901.2069.15.camel@laptop-linux> Message-ID: References: <1073672901.2069.15.camel@laptop-linux> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1092 Lines: 31 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/