Date: Wed, 23 May 2018 09:39:03 +1200
From: Thomas Munro <munro@ip9.org>
To: Dimitry Andric <dim@freebsd.org>
Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-hackers@freebsd.org
Subject: Re: printf("%m") doesn't generate a warning -- shouldn't it?
Message-ID: <CADLWmXXtZ6HeC=9gN7FzWg0=XOxweT_45jEB0HqmGW=Kho01yA@mail.gmail.com>
In-Reply-To: <77D988F8-ED6A-4F74-B81B-69BE4CC1D5FA@FreeBSD.org>
References: <CADLWmXU__ZRaS=gg_Y18WYbJJgk2Rs065RhkYmAZCFY8mp1Wjg@mail.gmail.com> <BAD690AA-C51A-4125-8F23-B637758C8EB6@FreeBSD.org> <20180521134306.GT6887@kib.kiev.ua> <77D988F8-ED6A-4F74-B81B-69BE4CC1D5FA@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22 May 2018 at 22:39, Dimitry Andric <dim@freebsd.org> wrote: > On 21 May 2018, at 15:43, Konstantin Belousov <kostikbel@gmail.com> wrote: >> Why not add %m instead ? It is very easy and several people did it in >> round-about ways. > > Sure, that is certainly a nice thing to have, and let's commit it. +1 > But > it's still an upstream bug if an explicit warning flag for non-ISO > printf specifiers doesn't work. I'll take that discussion to the LLVM > bug tracker. Thanks. Agreed. Also, even if %m is committed, older FreeBSD releases will be affected for some time, and many other operating systems are too.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLWmXXtZ6HeC=9gN7FzWg0=XOxweT_45jEB0HqmGW=Kho01yA>