Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: PATCH: maxfilelocks in ulimit output

X-seq: zsh-workers 18212
From: Clint Adams <clint@xxxxxxx>
To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
Subject: Re: PATCH: maxfilelocks in ulimit output
Date: Sun, 9 Feb 2003 12:29:12 -0500
Cc: zsh-workers@xxxxxxxxxx
In-reply-to: <1030209022500.ZM28201@xxxxxxxxxxxxxxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <20030209010655.GA10509@xxxxxxxx> <20030209014102.GA15743@xxxxxxxxxxx> <1030209022500.ZM28201@xxxxxxxxxxxxxxxxxxxxxxx>

> If you figure it out, I'd love to know.

GNU cpp 3.2 info says:

   * Identifiers that are not macros, which are all considered to be the
     number zero.  This allows you to write `#if MACRO' instead of
     `#ifdef MACRO', if you know that MACRO, when defined, will
     always have a nonzero value.  Function-like macros used
     without their function call parentheses are also treated as zero.

Seems that it's treating RLIMIT_AS and RLIMIT_RSS as
"identifiers", because they compare equally in the #if.

Follow-Ups:
- Re: PATCH: maxfilelocks in ulimit output
  - From: Clint Adams

References:
- PATCH: maxfilelocks in ulimit output
  - From: Clint Adams
- Re: PATCH: maxfilelocks in ulimit output
  - From: Clint Adams
- Re: PATCH: maxfilelocks in ulimit output
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author