public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH 2/2] Provide <memory.h>
Date: Tue, 22 Nov 2016 16:00:00 -0000	[thread overview]
Message-ID: <20161122160023.GB7595@calimero.vinschen.de> (raw)
In-Reply-To: <d8e75d06-4529-9bc7-19bc-c538bd6619b2@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]

On Nov 22 09:49, Eric Blake wrote:
> On 11/22/2016 12:59 AM, Sebastian Huber wrote:
> > Provide <memory.h> for all standard Newlib targets and remove
> > Cygwin-specific header.  Most POSIX like systems provide this historic
> > header.
> > 
> > Signed-off-by: Sebastian Huber <sebastian.huber@embedded-brains.de>
> > ---
> >  newlib/libc/include/memory.h   |  4 ++++
> >  winsup/cygwin/include/memory.h | 15 ---------------
> >  2 files changed, 4 insertions(+), 15 deletions(-)
> >  create mode 100644 newlib/libc/include/memory.h
> >  delete mode 100644 winsup/cygwin/include/memory.h
> > 
> > diff --git a/newlib/libc/include/memory.h b/newlib/libc/include/memory.h
> > new file mode 100644
> > index 0000000..f4a14fc
> > --- /dev/null
> > +++ b/newlib/libc/include/memory.h
> > @@ -0,0 +1,4 @@
> > +#ifndef _MEMORY_H
> > +#define	_MEMORY_H
> > +#include <string.h>
> > +#endif /* !_MEMORY_H */
> 
> Would it be worth adding
> 
> #warn This header is deprecated; consider using <string.h>
> 
> to get people to modernize their code?

Nice idea, but glibc is not doing that either...


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-11-22 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22  6:59 [PATCH 1/2] Declare non-standard pthread_yield() Sebastian Huber
2016-11-22  6:59 ` [PATCH 2/2] Provide <memory.h> Sebastian Huber
2016-11-22 15:49   ` Eric Blake
2016-11-22 16:00     ` Corinna Vinschen [this message]
2016-11-22 15:59   ` Corinna Vinschen

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=20161122160023.GB7595@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=newlib@sourceware.org \
    /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).