On Fri, 14 Jun 2019 at 03:17, Masahiro Yamada
wrote:
> On Fri, Jun 14, 2019 at 2:58 AM David A. Wheeler
> wrote:
> >
> > On Thu, 13 Jun 2019 18:18:15 +0100, Tim Murphy
> wrote:
> > > builtin functions can check their arguments to some extent.
> Interesting to
> > > wonder if user defined ones c
Wouldn't it be safer to disable specific warnings for specific target(s),
or specific sections of a makefile?
On Tue, 11 Jun 2019 at 19:42, Paul Smith wrote:
> On Tue, 2019-06-11 at 14:37 -0400, David A. Wheeler wrote:
> > Create a new make special variable "MAKE_SILENCEWARNINGS".
>
> I have to
On Fri, Jun 14, 2019 at 2:58 AM David A. Wheeler wrote:
>
> On Thu, 13 Jun 2019 18:18:15 +0100, Tim Murphy wrote:
> > builtin functions can check their arguments to some extent. Interesting to
> > wonder if user defined ones can.
> > we don't even have $(equals) or a way to know the number of arg
On Fri, Jun 14, 2019 at 4:16 AM Tim Murphy wrote:
>
> builtin functions can check their arguments to some extent. Interesting to
> wonder if user defined ones can.
> we don't even have $(equals) or a way to know the number of arguments that
> were supplied or any mathematical operations with whi
builtin functions can check their arguments to some extent. Interesting to
wonder if user defined ones can.
we don't even have $(equals) or a way to know the number of arguments that
were supplied or any mathematical operations with which to compare. So when
something is called wongly it charges on
On Thu, 13 Jun 2019 18:18:15 +0100, Tim Murphy wrote:
> builtin functions can check their arguments to some extent. Interesting to
> wonder if user defined ones can.
> we don't even have $(equals) or a way to know the number of arguments that
> were supplied or any mathematical operations with whi
