[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gcc
Subject:    Re: GCC warnings for unused global variables
From:       Marc Espie <espie () quatramaran ! ens ! fr>
Date:       2003-05-01 11:00:21
[Download RAW message or body]

In article <20030430083713.GU4016@paradies.suse.de> you write:
>* Alexander Kabaev (ak03@gte.com) [20030429 22:57]:
>
>> #ifndef lint
>> static const char rcsid[] =
>>   "$Id: src/dir/file.c 1.12 1999/08/27 23:45:12 me Exp$";
>> #endif /* not lint */
>
>Why not just use __attribute__((__unused__))?
>
>Philipp

Because it's a gcc extension, so writing portable code that
uses it will require some more machinery, hence more clutter.

Also, this kind of thing is pervasive in older code.

And warning on perfectly legal, innocuous constructs makes
absolutely no sense to me.

Using static char * variables (lately, const char *) to embed
version strings in files has been current practice over the last
twenty years or so. Why break it now ?
[prev in list] [next in list] [prev in thread] [next in thread]