This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: agressive fixincludes
- To: Joern Rennecke <amylaar at cygnus dot co dot uk>
- Subject: Re: agressive fixincludes
- From: Steven W Orr <steveo at world dot std dot com>
- Date: Tue, 23 Nov 1999 13:25:14 -0500
- cc: Per Bothner <per at bothner dot com>, ddsinc09 at ix dot netcom dot com, gcc at gcc dot gnu dot org
- Reply-To: steveo at world dot std dot com
Sorry, I just have to jump in with my $.02 worth.
ii = 44;
p = ⅈ
*p = ii/*p;
ii++; /* Don't forget to increment ii. */
printf ( "ii = %d\n", *p );
I know. It's similar to the example below.
:-)
--
----------Time flies like the wind. Fruit flies like a banana.----------------
--------Stranger things have happened but none stranger than this.-------------
Steven W. Orr steveo@world.std.com <site of former bang addr:-)>
---------------"Listen to me! We are all individuals."-------------------------
On Tue, 23 Nov 1999, Joern Rennecke wrote:
=>> The first question is: Is there any reason to fix C++-style comments
=>> *at all*? If they work for C, C++, and Objective-C, why do we bother
=>> fixing them?
=>
=>It doesn't work for C. It does work for recent versions of Gnu C.
=>
=>a = b //* This is a comment */
=>c;
=>
=>a=a//* Note that division acts differently than shifts for signed values. */2
=>;
=>