Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: sjackman@gmail.com, rearnsha@gcc.gnu.org, gdb-patches@sources.redhat.com
Subject: Re: sim/arm/armos.c: IsTTY [PATCH]
Date: Sun, 18 Sep 2005 19:13:00 -0000	[thread overview]
Message-ID: <uk6he5gwd.fsf@gnu.org> (raw)
In-Reply-To: <200509180903.j8I93fTo025933@elgar.sibelius.xs4all.nl> (message from Mark Kettenis on Sun, 18 Sep 2005 11:03:41 +0200 (CEST))

> Date: Sun, 18 Sep 2005 11:03:41 +0200 (CEST)
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> CC: eliz@gnu.org, sjackman@gmail.com, rearnsha@gcc.gnu.org,
>         gdb-patches@sources.redhat.com
> 
> FWIW, the correct way to deal with these issues is to dynamically
> allocate the buffer, making the buffer bigger if it fails because the
> buffer is too small:
> 
>   #ifndef _POSIX_PATH_MAX
>   #define _POSIX_PATH_MAX 256
>   #endif
> 
>   size_t len = _POSIX_PATH_MAX;
>   char *buf = xmalloc(len);
>   while (foo(..., buf, len) == -1 && errno == ENAMETOOLONG)
>     {
>       len *= 2;
>       buf = xrealloc(buf, len);
>     }
> 
> I used _POSIX_PATH_MAX here, but you could probably just as well
> hardcode a sensible value.  Don't forget to free the buffer once
> you're done with it ;-).

Forgive my bluntness, but if such a simple job requires such
complicated code, and with caveats on top of that, it's a clear sign
of a botched API, worthy of a certain company from Redmond!


      reply	other threads:[~2005-09-18 19:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 21:19 Shaun Jackman
2005-08-22 18:51 ` Shaun Jackman
2005-08-30  2:38 ` Daniel Jacobowitz
2005-09-06 16:22   ` Richard Earnshaw
2005-09-07 16:51   ` Shaun Jackman
2005-09-08  9:07     ` Richard Earnshaw
2005-09-08 19:28       ` Eli Zaretskii
2005-09-09 17:16       ` Shaun Jackman
2005-09-09 17:23       ` Shaun Jackman
2005-09-17 22:37         ` Daniel Jacobowitz
2005-09-17 23:32           ` Shaun Jackman
2005-09-18  1:14             ` Daniel Jacobowitz
2005-09-18  2:40               ` Shaun Jackman
2005-09-18  2:59                 ` Daniel Jacobowitz
     [not found]                 ` <20050918025653.GA4285@nevyn.them.org>
     [not found]                   ` <7f45d93905091720161f61e995@mail.gmail.com>
     [not found]                     ` <20050918033152.GA6546@nevyn.them.org>
2005-10-13 20:30                       ` Shaun Jackman
2005-10-19 16:12                 ` Shaun Jackman
2005-11-17 10:49                   ` Daniel Jacobowitz
2005-11-17 15:54                     ` Shaun Jackman
2005-09-18  3:32           ` Eli Zaretskii
2005-09-18  3:44             ` Daniel Jacobowitz
2005-09-18  9:04               ` Mark Kettenis
2005-09-18 19:13                 ` Eli Zaretskii [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uk6he5gwd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=rearnsha@gcc.gnu.org \
    --cc=sjackman@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox