>
> On Mon, Sep 11, 2017 at 11:48:47AM -0400, Frediano Ziglio wrote:
> > >
> > > On Mon, Sep 11, 2017 at 11:15:42AM +0100, Frediano Ziglio wrote:
> > > > Usually configuration macros are defined to 0 or undefined.
> > > > For this reason these macros are sometimes checked using #if
> > > > and
On Mon, Sep 11, 2017 at 11:48:47AM -0400, Frediano Ziglio wrote:
> >
> > On Mon, Sep 11, 2017 at 11:15:42AM +0100, Frediano Ziglio wrote:
> > > Usually configuration macros are defined to 0 or undefined.
> > > For this reason these macros are sometimes checked using #if
> > > and sometimes with
>
> On Mon, Sep 11, 2017 at 11:15:42AM +0100, Frediano Ziglio wrote:
> > Usually configuration macros are defined to 0 or undefined.
> > For this reason these macros are sometimes checked using #if
> > and sometimes with #ifndef/#ifdef.
> > As this macro is always defined with 0 or 1 it makes no
On Mon, Sep 11, 2017 at 11:15:42AM +0100, Frediano Ziglio wrote:
> Usually configuration macros are defined to 0 or undefined.
> For this reason these macros are sometimes checked using #if
> and sometimes with #ifndef/#ifdef.
> As this macro is always defined with 0 or 1 it makes no sense
> to
Usually configuration macros are defined to 0 or undefined.
For this reason these macros are sometimes checked using #if
and sometimes with #ifndef/#ifdef.
As this macro is always defined with 0 or 1 it makes no sense
to check if defined or not so check the code to avoid this
mistake.
