From mboxrd@z Thu Jan  1 00:00:00 1970
Path: main.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@elta.co.il>
Newsgroups: gmane.emacs.devel
Subject: Re: lim_data too narrow
Date: 22 Dec 2003 08:17:27 +0200
Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org
Message-ID: <uu13ttlzc.fsf@elta.co.il>
References: <200312180058.hBI0wtaq054209@bigtex.jrv.org>
	<E1AYHMK-0005K1-Du@fencepost.gnu.org>
Reply-To: Eli Zaretskii <eliz@elta.co.il>
NNTP-Posting-Host: deer.gmane.org
X-Trace: sea.gmane.org 1072074199 16184 80.91.224.253 (22 Dec 2003 06:23:19 GMT)
X-Complaints-To: usenet@sea.gmane.org
NNTP-Posting-Date: Mon, 22 Dec 2003 06:23:19 +0000 (UTC)
Cc: james@jrv.org, emacs-devel@gnu.org
Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Dec 22 07:23:14 2003
Return-path: <emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org>
Original-Received: from quimby.gnus.org ([80.91.224.244])
	by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian))
	id 1AYJTG-0004mM-00
	for <emacs-devel@deer.gmane.org>; Mon, 22 Dec 2003 07:23:14 +0100
Original-Received: from monty-python.gnu.org ([199.232.76.173])
	by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian))
	id 1AYJTG-00027T-00
	for <emacs-devel@quimby.gnus.org>; Mon, 22 Dec 2003 07:23:14 +0100
Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org)
	by monty-python.gnu.org with esmtp (Exim 4.24)
	id 1AYKKf-0000BB-KQ
	for emacs-devel@quimby.gnus.org; Mon, 22 Dec 2003 02:18:25 -0500
Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24)
	id 1AYKKM-00007N-Dp
	for emacs-devel@gnu.org; Mon, 22 Dec 2003 02:18:06 -0500
Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24)
	id 1AYKJq-0007xs-2Q
	for emacs-devel@gnu.org; Mon, 22 Dec 2003 02:18:05 -0500
Original-Received: from [207.232.27.5] (helo=WST0054)
	by monty-python.gnu.org with asmtp (Exim 4.24)
	id 1AYKJl-00070i-SE; Mon, 22 Dec 2003 02:17:32 -0500
Original-To: rms@gnu.org
In-reply-to: <E1AYHMK-0005K1-Du@fencepost.gnu.org> (message from Richard
	Stallman on Sun, 21 Dec 2003 23:07:56 -0500)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Emacs development discussions.  <emacs-devel.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org
Xref: main.gmane.org gmane.emacs.devel:18789
X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18789

> From: Richard Stallman <rms@gnu.org>
> Date: Sun, 21 Dec 2003 23:07:56 -0500
> 
> It would seem that on a 64-bit machine, lim_data should
> be a 64-bit type.  Is there any agreement on how to
> specify such a type in C?

Modern compilers should support the int64_t type (it is mandated by
the new C99 standard and should be defined on stdint.h).

> We could use configure to check whether rlim_t is defined
> in some header file.  What header file should it be in?

According to Posix, it should be in sys/resource.h.