This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
John, >Date: Fri, 27 Dec 1996 17:09:49 -0500 (EST) >From: address@hidden (John Sheldon) >Organization: Princeton/GFDL >To: address@hidden (Steve Emmerson) >Subject: Re: 961227: F90 standard "byte" (reprise) >Keywords: 199612271722.KAA28950 In the above message you wrote: > THAT DID IT! Well, it got thru the "make test", anyway. I'll have our > 'epcf90' user here test his code using it and let you know how things > turn out. Great! > > The one downside to all this is that if it does the trick for 'epcf90', > I will likely have to make changes to some interface routines I've > written here which help users write netCDF files. This means I'll have > to figure out how to handle BYTE's so that I am consistent with > "FORTRAN_HAS_NO_BYTE" and "`FILBYTEMACRO',`129'". Sigh.... Tell 'em to use C! ;-) -------- Steve Emmerson <address@hidden>