All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Serice <paul@serice.net>
To: Olivier Galibert <galibert@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org
Subject: Re: [PATCH] Avoid C++ comments, use C comments instead
Date: Mon, 10 Jul 2006 14:14:17 -0500	[thread overview]
Message-ID: <44B2A709.8020500@serice.net> (raw)
In-Reply-To: <20060710114117.GA62514@dspnet.fr.eu.org>

> Given than you can find gcc on pretty much everything that has a
> filesystem cache decent enough to handle git correctly, is this cost
> worth it?  _That_ was the question.

I've seen this argument before.  Unfortunately it seems reasonable
enough on the surface, and I actually bought into it much to may later
regret.

My experience is that gcc often produces buggy code, and if gcc is not
_the_ compiler for that platform, those bugs do not get fixed.
Specifically, I have had lots of problems with gcc and IRIX.

If you want to write portable code, you have to take into account
different operating systems _and_ different compilers.  Writing your
code for just a single compiler is almost as bad as writing your code
for just a single operating system.

Paul Serice

  reply	other threads:[~2006-07-10 19:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10  6:57 [PATCH] Avoid C++ comments, use C comments instead Pavel Roskin
2006-07-10  7:46 ` Junio C Hamano
2006-07-10  9:46   ` Olivier Galibert
2006-07-10 11:06     ` Johannes Schindelin
2006-07-10 11:41       ` Olivier Galibert
2006-07-10 19:14         ` Paul Serice [this message]
2006-07-10 20:24           ` Olivier Galibert
2006-07-10 22:55             ` Johannes Schindelin
2006-07-10 23:25               ` Yakov Lerner
2006-07-10 23:51                 ` Olivier Galibert
2006-07-11  0:15                   ` Shawn Pearce
2006-07-11  0:34                     ` Junio C Hamano
2006-07-10 23:42               ` Olivier Galibert
2006-07-11  5:17         ` Pavel Roskin

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=44B2A709.8020500@serice.net \
    --to=paul@serice.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=galibert@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.