All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: [RFC] Is it okay to just use GNU extensions or should an alternative be provided too?
Date: Sat, 16 Aug 2008 14:05:25 +0200	[thread overview]
Message-ID: <1218888325.4051.17.camel@fz.local> (raw)

I just talked with Marco on IRC.

I have just used asprintf in one of my patches, but now I discovered:
http://grub.enbug.org/BuildingOnNonGnu

So I became a bit unsure now if it's okay to just use asprintf.

Is it okay to just use and don't care about enviroments which don't
use/have glibc?

Or should such GNU extentions just not be used if they can be avoided?

I doubt it would be good to use many `#ifdef _GNU_SOURCE' in the code.




             reply	other threads:[~2008-08-16 12:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-16 12:05 Felix Zielcke [this message]
2008-08-16 12:32 ` [RFC] Is it okay to just use GNU extensions or should an alternative be provided too? Vesa Jääskeläinen
2008-08-16 12:39   ` Robert Millan
2008-08-16 12:43   ` Felix Zielcke
2008-08-16 12:54     ` Vesa Jääskeläinen
2008-08-16 12:58     ` Robert Millan
2008-08-16 12:39 ` Robert Millan
2008-08-16 12:48   ` Felix Zielcke

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=1218888325.4051.17.camel@fz.local \
    --to=fzielcke@z-51.de \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.