Re: Checks for getcwd(NULL, 0) and get_current_dir_name()

To: Guillem Jover <guillem@debian.org>
Cc: Svante Signell <svante.signell@telia.com>, debian-hurd@lists.debian.org, Bug hurd mailing list <bug-hurd@gnu.org>
Subject: Re: Checks for getcwd(NULL, 0) and get_current_dir_name()
From: Roland McGrath <roland@hack.frob.com>
Date: Sat, 20 Oct 2012 10:21:03 -0700 (PDT)
Message-id: <[🔎] 20121020172103.E4C802C077@topped-with-meat.com>
In-reply-to: Guillem Jover's message of Saturday, 20 October 2012 05:49:25 +0200 <[🔎] 20121020034925.GA13338@gaara.hadrons.org>
References: <1349970393.29093.234.camel@s1499.it.kth.se> <[🔎] 20121017090728.GF5583@type.bordeaux.inria.fr> <[🔎] 1350466018.29093.336.camel@s1499.it.kth.se> <[🔎] 201210171151.38392.pino@debian.org> <[🔎] 1350476147.29093.340.camel@s1499.it.kth.se> <[🔎] 20121017141510.GA14801@gaara.hadrons.org> <[🔎] 1350484347.29093.369.camel@s1499.it.kth.se> <[🔎] 1350488543.29093.379.camel@s1499.it.kth.se> <[🔎] 1350629757.5747.62.camel@hp.my.own.domain> <[🔎] 20121020034925.GA13338@gaara.hadrons.org>

I'm pretty sure we were the first to support that behavior.  (GNU has had a
strong commitment to avoiding static limits from the beginning.)  Not that
it matters for choosing a feature macro name.  The best names for such
things are purely descriptive rather than referring to a system by name
anyway.  i.e., HAVE_GETCWD_NULL_MALLOCS or suchlike.

Reply to:

Follow-Ups:
- Re: Checks for getcwd(NULL, 0) and get_current_dir_name()
  - From: Guillem Jover <guillem@debian.org>

References:
- Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream
  - From: Samuel Thibault <sthibault@debian.org>
- Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream
  - From: Svante Signell <svante.signell@telia.com>
- Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream
  - From: Pino Toscano <pino@debian.org>
- Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream
  - From: Svante Signell <svante.signell@telia.com>
- Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream
  - From: Guillem Jover <guillem@debian.org>
- Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream
  - From: Svante Signell <svante.signell@telia.com>
- Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream
  - From: Svante Signell <svante.signell@telia.com>
- Re: Checks for getcwd(NULL, 0) and get_current_dir_name()
  - From: Svante Signell <svante.signell@telia.com>
- Re: Checks for getcwd(NULL, 0) and get_current_dir_name()
  - From: Guillem Jover <guillem@debian.org>

Prev by Date: Re: Checks for getcwd(NULL, 0) and get_current_dir_name()
Next by Date: Re: Checks for getcwd(NULL, 0) and get_current_dir_name()
Previous by thread: Re: Checks for getcwd(NULL, 0) and get_current_dir_name()
Next by thread: Re: Checks for getcwd(NULL, 0) and get_current_dir_name()
Index(es):
- Date
- Thread