This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: I don't understand some of gcc-4.1-20070514, a patch here.
- From: Bernd Jendrissek <berndj at prism dot co dot za>
- To: "J.C. Pizarro" <jcpiza at gmail dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 22 May 2007 13:13:23 +0200
- Subject: Re: I don't understand some of gcc-4.1-20070514, a patch here.
- References: <998d0e4a0705211447o33547c6cue7b221ff609b61de@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, May 21, 2007 at 11:47:15PM +0200, J.C. Pizarro wrote:
> http://en.wikipedia.org/wiki/Brainfuck
If you're going to insult the contributors to GCC's code base by
comparing the code they work on to bf, then I think you should write
better English than the following:
> I'm saying is that you do not develop the source code directly to machine
> and distantly to the human natural language.
>
> The lecture of the legible source code is more important than brainfucking
> the source code for maximum speed.
Let the one that is without sin cast the first stone, hey? I don't
understand what you mean by "distantly" or "lecture", for example.
> I hate "if (ptr) { ... }" /* <- It's b-r-a-i-n-f-u-c-k-e-d source code! */
> I love "if (ptr != NULL) { ... }"
Personally, I find the former idiom more readable. It doesn't require
me to visually and cognitively distinguish between "==" and "!=".
That's my personal choice, but I won't die, and nor will I hurl insults
if other people want to choose differently.
http://c2.com/cgi/wiki?PersonalChoiceElevatedToMoralImperative
If you really want to contribute to the Free Software movement, then my
personal advice to you is to show a bit more respect to the people who
make it happen. A compiler collection like GCC is a mature, large and
complicated piece of software; a lot of work has gone into making it and
there are some very very clever people working on it - certainly
cleverer than you or I. You should show some humility for what has come
and gone before you: everything you see in the code base has a reason
for being there, and if you can't tell what that reason is, it means YOU
haven't thought about it hard enough.
- --
Seen in comp.lang.c:
> cody wrote:
>> The problem is that i believe that my assertions are correct.
> Yes, that is a problem.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGUtBHwyMv24BBd/gRAno7AJ9VoHb2PoEpEeB8dvg8vy5pzhN32wCgkAnK
N/XuV3jJ+YQZLIQusJTzs0o=
=46X2
-----END PGP SIGNATURE-----