Date: Wed, 30 Jan 2002 02:40:16 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Jeroen Ruigrok/asmodai <asmodai@wxs.nl> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, Jordan Hubbard <jkh@winston.freebsd.org>, Dallas De Atley <deatley@apple.com>, arch@FreeBSD.ORG Subject: Re: __P macro question Message-ID: <3C57CD90.351F9AD5@mindspring.com> References: <21280.1012384756@critter.freebsd.dk> <3C57C858.5FCC9453@mindspring.com> <20020130103326.GJ22384@daemon.ninth-circle.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeroen Ruigrok/asmodai wrote: > Anyway, are you scared of ANSI C? > Your argumentation is starting to border on the point of fright of > moving forward to a standard a bit closer to what people are actually > taught in schools nowadays. Microsoft Visual C++? 8-). > Most people don't even KNOW K&R C anymore, let alone use it. So moving > to an ANSI standard in today's world might even be better to continue to > act as a reference platform. ANSI C is less portable than K&R C, and ANSI compilers will compile K&R C. I would suggest avoiding bitfields, and byte order dependent coding, too, if you want the code to be portable. > Backporting is already a pain in the arse, having just recently been > through backporting Scott Long's UDF driver to STABLE. And that's new > code not even in CURRENT nor in STABLE, just making use of the APIs and > supplied functionality. Then by all means, make it even harder, for aesthetic reasons. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C57CD90.351F9AD5>