[netCDF #CTW-339617]: netcdf version check

> Thanks! -John
>
> > -----Original Message-----
> > From: Unidata netCDF Support [mailto:address@hidden]
> > Sent: Wednesday, June 11, 2008 4:52 PM
> > To: address@hidden
> > Cc: address@hidden; address@hidden;
> > address@hidden; address@hidden; address@hidden; address@hidden
> > Subject: [netCDF #CTW-339617]: netcdf version check
> >
> > Hi John,
> >
> > Sorry to have been unresponsive, we've been doing final testing before a
> > release.
> >
> > > Assuming that the nf_format_64bit parameter were defined, but the
> > configure
> > > script determined that for the given installation, large file offsets
> > were
> > > not available, would it be an error to do this?
> > >
> > > NF_CREATE(FileName, OR(NF_CLOBBER,NF_64BIT_OFFSET), DH%NCID)
> >
> > I believe that would be a harmless no-op.  I don't have any platforms here
> > to test
> > on that don't support LFS, so I can't just run a test easily.  But the
> > above should
> > work fine even on platforms that don't support LFS.  A "file too large"
> > error would
> > occur in case this program later tried to write a file > 2 GiB in size. but
> > things
> > would work fine up to that poiunt, and the file created would have 64-bit
> > offsets.
> >
> > --Russ
> >
> > Russ Rew                                         UCAR Unidata Program
> > address@hidden                     http://www.unidata.ucar.edu
> >
>

Howdy!

I would also add that if netcdf is built with --enable-large-file-tests you
will learn at build time whether a platform supports large files.

Don't confuse large files with 64-bit offset files. Although 64-bit offset
files can be greater than 2 GB, so can classic format files. The large file
issue has to do with how big files can get on your disk. It doesn't matter what
format they are in...

Thanks,

Ed

Ticket Details
===================
Ticket ID: CTW-339617
Department: Support netCDF
Priority: Normal
Status: Closed