From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1d5d51400604072118t285ca315w5531a5a251676948@mail.gmail.com> Date: Sat, 8 Apr 2006 12:18:45 +0800 From: "Fernan Bolando" To: 9fans@cse.psu.edu Subject: Re: [9fans] Good enough approximation for ape/pcc In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1d5d51400604071201n5f308eeco519feb9d76023d62@mail.gmail.com> Topicbox-Message-UUID: 3303ec62-ead1-11e9-9d60-3106f5b1d025 On 4/8/06, uriel@cat-v.org wrote: > Writing code that will compile with ?c is just matter good style, ie., > not (ab)using cpp, not using gcc extensions and so on; see > /sys/doc/comp.ps for details. Ape doesn't not even come into the > picture, no sane C code should ever need to use cpp(1) > > Figuring out if the builtin preprocessor will handle your code should > be obvious, but if you really want to test, you could use the port of > the compilers that is part of Inferno. > > And if you have the disgrace of having to write software under lunix, > I would recommend using the p9p libs and doing native ports > to Plan 9. Or just use Limbo and Inferno and be happy. > > Ape is an unfortunate historical aberration, lets leave it at that and > not write new code that depends on it. My skills are not always good enough to port everything to plan9 natively. I am also apprehensive to port some stuff natively because, some of the stu= ff that where ported native IMO had far too much structural change that it wou= ld be difficult to merge back to the orginal code. I dont want to end up using code from projects that I like and not be able to contribute to it.( assuming I have something to offer ) New codes should be written in p9p or plan9 native, But for other poeples project they should be the one to decide I guess.As I understand it this was the main reason ape was created How do you guys handle this type of situation? -- Public PGP/GnuPG key (http://www.fernski.com) pub 1024D/3576CA71 2006-02-02 Fernan Bolando Key fingerprint =3D FDFE C9A8 FFED C1A5 2F5C EFEB D595 AF1C 3576 CA71