This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/60639] New Assert Variants
- From: "pinskia at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 24 Mar 2014 21:29:32 +0000
- Subject: [Bug c/60639] New Assert Variants
- Auto-submitted: auto-generated
- References: <bug-60639-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60639
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Olaf van der Spek from comment #4)
> (In reply to Andrew Pinski from comment #3)
> > Well don't call it assert, call it my_assert or something like that.
> >
> > We should not be adding random extensions if they can be done other places.
>
> Then what is the criteria for including something in GCC (or libc)?
If it is part of a standard or is needed for a language feature is the criteria
for GCC/glibc.
> And what'd be a better place?
Your own library.
>
> > Also I think assert.h comes from libc and not GCC.
>
> glibc?
well it depends on your target but for GNU/Linux, it is glibc. For
Android/Linux, it is bionic. But there are other libc's besides those two out
there for Linux.