Portability guidelines?

Article View: gnu.misc.discuss

Article #75127

#75127

From: Graham Toal
Date: Thu, 08 Nov 1990 01:05

22 lines
1505 bytes

Is there a gnu document on how to write code portably, so that it
stands an even chance of compiling on any arbitrary machine? (I've
seen the coding standards document; not what I'm looking for)

If there isn't one, I'll write it, since over the last six months
I've learned a lot about the sort of pitfalls one meets.  I know
that gnu isn't actively supporting anything other than unix, but
writing portable code is good practice in any case.  I'm talking
about ways of simplifying things, rather than suggesting that your
code is littered with #ifdef's.

If anyone has any particular horror stories about 'gotcha's' in
porting, I'd welcome mail.  Especially with examples -- as short
as is reasonable, to add to the document.

Thanks,
  Graham  <gtoal@ed.ac.uk>  (via nsfnet-relay preferably)

PS I answer *all* mail, so no reply means one of us can't reach the other.
-- 
(* Posted from tharr.uucp - Public Access Unix - +44 (234) 261804 *)

Technical Details

Message-ID: <1396@tharr.UUCP>

Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!ukc!axion!tharr!gtoal

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1025b4,767e29d110ceceb5,start
X-Google-Attributes: gid1025b4,public
X-Google-ArrivalTime: 1990-11-07 17:05:17 PST
Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!ukc!axion!tharr!gtoal
From: gtoal@tharr.UUCP (Graham Toal)
Newsgroups: gnu.misc.discuss
Subject: Portability guidelines?
Message-ID: <1396@tharr.UUCP>
Date: 8 Nov 90 01:05:17 GMT
Reply-To: gtoal@ed.ac.uk (Graham Toal)
Distribution: gnu
Organization: Public access to Usenet in the UK
Lines: 22
Posted: Thu Nov  8 02:05:17 1990