[17503] in Kerberos_V5_Development
Re: Proposed platform assumption changes
daemon@ATHENA.MIT.EDU (Nico Williams)
Wed Feb 1 11:24:31 2012
MIME-Version: 1.0
In-Reply-To: <4F28EA4B.4050700@d6.com>
Date: Wed, 1 Feb 2012 10:24:25 -0600
Message-ID: <CAK3OfOgLvi0sfkUu7n_Eip8KFTyw2y7=UqrDsymGsDxakEy8nQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Chris Hecker <checker@d6.com>
Cc: Danilo Almeida <dalmeida@mit.edu>, Ken Raeburn <raeburn@mit.edu>,
"krbdev@mit.edu List" <krbdev@mit.edu>
Content-Type: text/plain; charset="utf-8"
Errors-To: krbdev-bounces@mit.edu
Content-Transfer-Encoding: 8bit
On Wed, Feb 1, 2012 at 1:31 AM, Chris Hecker <checker@d6.com> wrote:
> I find it surprising that a lot of people chiming in are so willing to
> give up the currently working build support for one of the (admittedly
> sadly) most used compilers in the world in exchange for pretty minor
> syntactic sugar. Seems crazy to me, but I guess I'm biased as one of
> the (apparently) few windows developers who builds krb5 instead of just
> links to prebuilt binaries. However, even if I did just link to it,
> I've found (and reported) a bunch of minor bugs, and so fixing those
> locally with the proposed mingw way to get designated initializers would
> require a completely different toolchain. Just doesn't seem worth it
> for this minor of a win.
It's not just syntactic sugar for me: it's sugar that cscope
[accidentally] (and other tools, no doubt) understands, which makes it
much easier to read a large code base.
But then, I'm not proposing that MSVC support be dropped. I'm
proposing that since this isn't about syntactic sugar for humans but
rather about tools finding assignments to struct fields, ugly macro or
other workarounds for MSVC are worthwhile.
Nico
--
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
