From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <3C3F92CD-00DC-41E2-960F-8E092A993F5D@orthanc.ca> From: Lyndon Nerenberg To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v912) Subject: Re: [9fans] Re: Ruby port Date: Mon, 12 Nov 2007 16:59:46 -0800 References: Topicbox-Message-UUID: f59dc6f2-ead2-11e9-9d60-3106f5b1d025 On 2007-Nov-12, at 11:39 , Steve Simon wrote: > Is the "problem" more the lack of g++ and perhaps > glibc than the gcc C compiler itself or am I > missing somthing. 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 -lyndon