mailing list of musl libc
 help / color / mirror / code / Atom feed
From: croco@openwall.com
To: musl@lists.openwall.com
Subject: Re: NULL
Date: Wed, 9 Jan 2013 17:09:27 +0400	[thread overview]
Message-ID: <20130109130927.GA2947@openwall.com> (raw)
In-Reply-To: <50ED4E45.6050801@barfooze.de>

Hi folks,

On Wed, Jan 09, 2013 at 12:02:29PM +0100, John Spencer wrote:

> so for me, there are 3 options how to deal with issue in the future:

> 2) change musl so it is compatible with those apps. this would mean:
> #if defined(__GNUC__) && defined(__cplusplus__)
> #define NULL __null
> #elif defined (__cplusplus__)
> #define NULL 0
> #else
> #define NULL (void *) 0 /* for C code */
> #end

> this change is the easiest solution: any problem will be magically fixed.

Actually, the problem is not fixed this way; this just gives the problem
the right (hmmm.. license, heh) to exist forever.  My experience of
teaching students shows that when smart people introduce something to help
stupid people to remain useful without learning, we end up with more people
who don't want to learn, and that's all (arhgggg, I hate the
one-unknown-to-me who decided one day that two object modules having global
variables of the same name and type should link successfully... so that
newbie can simply place 'int my_damn_var;' line into his/her header not
bothering with understanding of 'extern' and the linker as such, and then
they tend to ask the well-known thing 'why do you say this is incorrect if
it works')

However, sometimes the practice forces us to do wrong things just because
we have no time or resources to do what is the right, and it looks like
this is exactly the case.  So perhaps the "option 2" will finally be
choosen, despite we don't like it.  However, I'd suggest at least to let
the people know this is a WORKAROUND for the bugs THEY introduce: make this
hack disabled by default, enabled by a compile-time option, and issue a
warning which points them to this discussion or something similar.
Something like "Okay, if your program doesn't work without this workaround,
then you can use the workaround, but you'd better fix your program".  This
will not do much influence while musl is not so popular, but I hope it will
become popular one day (I really do... let's give the damn world a chance),
and then the people will have something to think about.


Thanks!

Andrey Stolyarov


  parent reply	other threads:[~2013-01-09 13:09 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09 11:02 NULL John Spencer
2013-01-09 12:18 ` NULL Szabolcs Nagy
2013-01-09 13:36   ` NULL John Spencer
2013-01-12  6:32     ` NULL Rob Landley
2013-01-12  6:46       ` NULL Rich Felker
2013-01-12  7:15         ` NULL Luca Barbato
2013-01-12 13:33           ` NULL Rich Felker
2013-01-12 11:39       ` NULL Jens Staal
2013-01-09 13:09 ` croco [this message]
2013-01-09 13:47   ` NULL John Spencer
2013-01-09 14:49     ` NULL croco
2013-01-09 14:42 ` NULL Luca Barbato
2013-01-09 14:47   ` NULL Rich Felker
2013-01-09 15:03     ` NULL Luca Barbato
2013-01-09 15:18     ` NULL John Spencer
2013-01-09 15:36       ` NULL Rich Felker
2013-01-09 21:11         ` NULL Rob
2013-01-09 21:53           ` NULL Szabolcs Nagy
2013-01-09 22:17             ` NULL Rob
2013-01-09 23:42         ` NULL Szabolcs Nagy
2013-01-12  6:56         ` NULL Rob Landley
2013-01-12  7:07           ` NULL Bobby Bingham
2013-01-12 13:31           ` NULL Rich Felker
2013-01-13 14:29             ` NULL Rob Landley
2013-01-13 14:56               ` NULL Luca Barbato
2013-01-13 16:29                 ` NULL Rob Landley
2013-01-13 17:14                   ` NULL Luca Barbato
2013-01-13 15:23               ` NULL Strake
2013-01-13 17:17                 ` NULL Luca Barbato
2013-01-13 17:47               ` NULL Szabolcs Nagy
2013-01-13 19:46                 ` NULL Rob Landley
2013-01-14  6:11                   ` NULL Rich Felker
2013-01-14  8:45                     ` musl as a framework to test applications' compatibility with POSIX (was: NULL) Vasily Kulikov
2013-01-14 14:03                       ` Rich Felker
2013-01-14 14:30                         ` Vasily Kulikov
2013-01-14 15:02                           ` Szabolcs Nagy
2013-01-14 15:14                           ` Rich Felker
2013-01-14 13:19                     ` NULL Rob Landley
2013-01-12  5:56 ` NULL Rob Landley
2013-01-12  6:42   ` NULL Rich Felker

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=20130109130927.GA2947@openwall.com \
    --to=croco@openwall.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).