From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 1/1] config.mk: Explicitly set used C and C++ standard
Date: Thu, 27 Apr 2017 15:10:33 +0200 [thread overview]
Message-ID: <20170427131032.GB14404@rei.lan> (raw)
In-Reply-To: <20170414122312.22734-1-pvorel@suse.cz>
Hi!
> IMHO If we really want to require old standard, we should explicitly say which one.
> I suppose passing a flag is appropriate way than to use c89 as CC variable.
Where do we say that we require old standard?
All I can think of is that we should produce portable code, which is
something completely different that sticking to a single C standard
revision...
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-04-27 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 12:23 [LTP] [RFC PATCH 1/1] config.mk: Explicitly set used C and C++ standard Petr Vorel
2017-04-27 13:10 ` Cyril Hrubis [this message]
2017-04-27 13:22 ` Petr Vorel
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=20170427131032.GB14404@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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.