Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ncar!gatech!purdue!haven!umd5!jupiter.astro.umd.edu!jjk
From: jjk@jupiter.astro.umd.edu (Jim Klavetter)
Newsgroups: comp.lang.c
Subject: moving towards the standard ANSI with old c code
Summary: how and when
Message-ID: <8452@umd5.umd.edu>
Date: 19 Apr 91 17:43:12 GMT
Sender: news@umd5.umd.edu
Reply-To: jjk@astro.umd.edu (Jim Klavetter)
Distribution: na
Organization: U of Md., Astronomy Program
Lines: 17

2 related sets of questions:

1.  What is the timescale for all compilers to be ANSI?  And what is
the timescale for most compilers not accepting old c (I know it is
often called K&R c, but I will use the term old C to mean nonANSI c)?

2.  When should I be worrying about updating my libraries (if not my
programs) to ANSI c?  Should this be done all at once or can I do it
as needed?

It is obvious that it needs to be done sometime, but when?

jjk@astro.umd.edu also for Athabasca and Reudi
Jim Klavetter
Astronomy
UMD
College Park, MD  20742