X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
Message-ID: <3FE89778.9090503@phekda.gotadsl.co.uk>
Date: Tue, 23 Dec 2003 19:28:56 +0000
From: Richard Dawe <rich AT phekda DOT gotadsl DOT co DOT uk>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031031
X-Accept-Language: en, de, fr
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: rlim_t
References: <usmjdtlok DOT fsf AT elta DOT co DOT il>
In-Reply-To: <usmjdtlok.fsf@elta.co.il>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Eli Zaretskii wrote:
> The latest Posix standard defines the rlim_t data type, which is the
> type used to specify limits in sys/resource.h.  I've looked at the
> current CVS, and we don't have rlim_t.  So how about adding
> 
>   typedef long rlim_t;
> 
> to sys/resource.h and then using rlim_t instead of long in both
> struct rlimit and struct rusage?  It sounds like a simple change.

Yes, that sounds fine. Perhaps you could define RLIM_SAVED_MAX and 
RLIM_SAVED_CUR at the same time? Perhaps they should be the same as 
RLIM_INFINITY (SUSv3/POSIX allows this).

Bye, Rich =]

-- 
Richard Dawe [ http://homepages.nildram.co.uk/~phekda/richdawe/ ]

"You can't evaluate a man by logic alone."
   -- McCoy, "I, Mudd", Star Trek