From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, tytso@mit.edu
Cc: gnehzuil.liu@gmail.com, linux-ext4@vger.kernel.org
Subject: Re: debugfs: dump a sparse file as a new sparse file
Date: 1 Jan 2013 16:25:04 -0500 [thread overview]
Message-ID: <20130101212504.11364.qmail@science.horizon.com> (raw)
In-Reply-To: <20130101205709.GC12554@thunk.org>
> There are people who compile e2fsprogs under Windows (e.g. for FUSE
> for Windows support), and MSVC does not support VLA's or C99 in
> general In general I tend to be very conservative about what compiler
> features are used in e2fsprogs, and I do care about portability beyond
> just Linux systems.
Ah, thank you! I fully agree that's an important C compiler to
target; I had just erroneously assumed that commercial C compilers
would try to be "check-box feature complete" on such matters.
But apparently Microsoft don't support C99 and have no intention to:
http://herbsutter.com/2012/05/03/reader-qa-what-about-vc-and-c99/
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2089423-c99-support
http://www.infoq.com/news/2012/05/vs_c99_support/
That's a good enough reason; my only remaining objection is calling it
"a non-standard/non-portable GCC extension".
next prev parent reply other threads:[~2013-01-01 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 4:07 debugfs feature request: dump sparse files as sparse George Spelvin
2012-11-15 14:46 ` [PATCH] debugfs: dump a sparse file as a new sparse file Zheng Liu
2013-01-01 2:08 ` Theodore Ts'o
2013-01-01 12:33 ` Zheng Liu
2013-01-01 20:10 ` George Spelvin
2013-01-01 20:57 ` Theodore Ts'o
2013-01-01 21:25 ` George Spelvin [this message]
2013-01-01 22:47 ` Theodore Ts'o
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=20130101212504.11364.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=gnehzuil.liu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.