Util-Linux package development
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Phillip Susi <psusi@ubuntu.com>, util-linux <util-linux@vger.kernel.org>
Subject: Re: libsmartcols patch
Date: Mon, 16 Feb 2015 14:46:28 +0100	[thread overview]
Message-ID: <20150216134628.GI11948@ws.net.home> (raw)
In-Reply-To: <20150216104848.GK4075@vapier>

On Mon, Feb 16, 2015 at 05:48:48AM -0500, Mike Frysinger wrote:
> > > general note: libraries should never assert/abort/exit.
> > 
> >  what about segfault?
> 
> that's a red herring.  you can't guarantee your codebase is bug free, but that 
> doesn't mean encouraging a policy of committing suicide is a good thing.

suicide + usable message is better than segfault

> >  We use assert to detect fatal internal library bugs, for mistakes in
> >  applications (e.g. incomplete arguments) it returns -EINVAL.
> 
> libsmartcols/src/table_print.c:
> int scols_print_table(struct libscols_table *tb)
> {
> ...
>     assert(tb);
>     if (!tb)
>         return -1;

this is mistake, fixed in libsmartcols and libmount, I'll later fix it
in libfdisk too.

> >  Its' possible to remove CONFIG_LIBSMARTCOLS_ASSERT from smartcolsP.h,
> >  but I don't think the library is already well tested.
> 
> odd ... why is that reimplementing the wheel ?  the standard assert.h already 
> supports NDEBUG for turning off asserts.
> 
> i see there's a bunch of such knobs in the codebase.  time for a 
> --{en,dis}able-asserts configure flag ?  you could delete all the existing 
> CONFIG_xxx_ASSERT defines and simply rely on configure adding -DNDEBUG to 
> CPPFLAGS.

Maybe, the idea has been to keep it in our hands and force people to
use asserts for the "not yet well tested" libs.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

      reply	other threads:[~2015-02-16 13:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29  1:30 libsmartcols patch Phillip Susi
2015-01-07 14:26 ` Karel Zak
2015-02-16  5:00 ` Mike Frysinger
2015-02-16 10:27   ` Karel Zak
2015-02-16 10:48     ` Mike Frysinger
2015-02-16 13:46       ` Karel Zak [this message]

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=20150216134628.GI11948@ws.net.home \
    --to=kzak@redhat.com \
    --cc=psusi@ubuntu.com \
    --cc=util-linux@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox