git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Avoid C++ comments, use C comments instead

From
PSPaul Serice <paul@serice.net>
Date
Jul 10, 2006, 19:14 UTC
Message-ID
<44B2A709.8020500@serice.net>
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
Previous: Olivier GalibertNext: Olivier Galibert
Message 6 of 14 in “Avoid C++ comments, use C comments instead”
  1. Avoid C++ comments, use C comments insteadPavel Roskin, Jul 10, 2006
  2. Junio C HamanoJul 10, 2006
  3. Olivier GalibertJul 10, 2006
  4. Johannes SchindelinJul 10, 2006
  5. Olivier GalibertJul 10, 2006
  6. Paul SericeJul 10, 2006
  7. Olivier GalibertJul 10, 2006
  8. Johannes SchindelinJul 10, 2006
  9. Yakov LernerJul 10, 2006
  10. Olivier GalibertJul 10, 2006
  11. Shawn PearceJul 11, 2006
  12. Junio C HamanoJul 11, 2006
  13. Olivier GalibertJul 10, 2006
  14. Pavel RoskinJul 11, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.