Date: Sat, 18 Apr 1998 10:44:21 -0400 (EDT) From: Thomas David Rivers <rivers@dignus.com> To: jkh@time.cdrom.com, rotel@indigo.ie Cc: bde@zeta.org.au, freebsd-bugs@hub.freebsd.org Subject: Re: bin/6332: time.h doesn't compile with -traditional Message-ID: <199804181444.KAA09701@lakes.dignus.com>
next in thread | raw e-mail | index | archive | help
> > > Couldn't agree more, all new code should use > > > > int main(int argc, char** argv) > > Or even: > > int > main(int argc, char *argv[]) > > If you ever want to create tags for the code. ;) > > Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" in the body of the message > Ok - before this degrades into the typical "ANSI is better" argument; let's just capitulate and say "yes - all new code should be ANSI." Now; let's examine another possible situation, which we may want to allow, or may want to not worry about. In my instance, I'm trying to write some rather portable software. This software has to compile, on other platforms, with a non-ANSI compiler... so, for that reason, I can only conditionally use ANSI-isms. In the past, I was using gcc -traditional on FreeBSD as a screening test before the software was compiled on the non-ANSI host. This would quickly catch issues and give the developer writing the code an opportunity to discover the issue before there had to be some massive "we've got to fix this to compile on platform X" issue later. If we decide that gcc -traditional isn't going to work with our system headers, then I can no longer employ that screening test (without editing the headers, which is what I've tended to do for several versions of FreeBSD now...) So - you see, I agree - all new code, when possible, should use the appropriate ANSI features... but I don't see a compeling reason to want to disallow those situations where we can't. [By the way, the host in question is an RS/6000 with IBM's XLC compiler, it has *way* too many bugs for us to use..., the non-ANSI version seems a little more robust... and, we can't upgrade to newer ones because we're stuck at AIX 3.2.5; for support reasons.] - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804181444.KAA09701>