public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Freddie Chopin <freddie_chopin@op.pl>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>,
		newlib@sourceware.org
Subject: Re: [PATCH v3 3/5] Introduce _REENT_GLOBAL_STDIO_STREAMS
Date: Thu, 09 Aug 2018 04:59:00 -0000	[thread overview]
Message-ID: <932842b778dccb3546c78f42d4c0a459f79b4344.camel@op.pl> (raw)
In-Reply-To: <7360fe32-cd12-5b49-1d1c-22a7b109cc49@embedded-brains.de>

On Wed, 2018-08-08 at 16:15 +0200, Sebastian Huber wrote:
> The thread-local IO streams are a Newlib feature that is used by our 
> applications.

Don't get me wrong, but I would expect an option with "global" in the
name to make the streams really global, not "sort-of-global" (;
Otherwise it looks like a half-baked-hack to fix just some particular
problem instead of looking at the whole picture.

Regards,
FCh

  reply	other threads:[~2018-08-08 15:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29 12:25 [PATCH v3 1/5] Remove superfluous parameter from std() Sebastian Huber
2017-06-29 12:25 ` [PATCH v3 4/5] Enable _REENT_GLOBAL_STDIO_STREAMS for RTEMS Sebastian Huber
2017-06-29 12:25 ` [PATCH v3 2/5] Add stdin_init(), stdout_init() and stderr_init() Sebastian Huber
2017-06-29 12:25 ` [PATCH v3 3/5] Introduce _REENT_GLOBAL_STDIO_STREAMS Sebastian Huber
2017-06-29 18:31   ` Corinna Vinschen
2017-06-30  5:43     ` Sebastian Huber
2017-06-30  8:13       ` Corinna Vinschen
2017-06-30  8:58         ` Sebastian Huber
2017-06-30 10:35           ` Corinna Vinschen
2018-08-08 14:10           ` Freddie Chopin
2018-08-08 15:20             ` Sebastian Huber
2018-08-09  4:59               ` Freddie Chopin [this message]
2018-08-09  6:09                 ` Sebastian Huber
2017-06-29 12:25 ` [PATCH v3 5/5] Add --enable-newlib-global-stdio-streams Sebastian Huber

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=932842b778dccb3546c78f42d4c0a459f79b4344.camel@op.pl \
    --to=freddie_chopin@op.pl \
    --cc=newlib@sourceware.org \
    --cc=sebastian.huber@embedded-brains.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).