From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 13 Nov 2007 02:23:01 +0100 From: Hagen Paul Pfeifer To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] Re: Ruby port Message-ID: <20071113012300.GL4572@c3po.0xdef.net> References: <3C3F92CD-00DC-41E2-960F-8E092A993F5D@orthanc.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <3C3F92CD-00DC-41E2-960F-8E092A993F5D@orthanc.ca> User-Agent: Mutt/1.5.13 (2006-08-11) Topicbox-Message-UUID: f5e4f75c-ead2-11e9-9d60-3106f5b1d025 On 2007.11.13 Lyndon Nerenberg pressed the following keys: >On 2007-Nov-12, at 11:39 , Steve Simon wrote: >I find that > 90% of the problem is code that makes use of all the >__(foo)__ attribute crud in function declarations. It shouldn't be >difficult to write a tool to strip that nonsense out. > >Alternatively you could teach the compilers to recognize and ignore >those constructs, but my personal preference is to just elide the bits >from the source at import. Even ignoring them lends them more >credibility than my morals allow ;-P A lot of GNU/Linux packages utilize gcc attributes - maybe the cleaner way is to let decide the compiler what to use or to ignore. It seems less stressful as dropping an additional pre-processor in the build chain. >-lyndon HGN