[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Open file mode status

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.

  • Subject: Re: Open file mode status
  • Date: Tue, 31 May 1994 16:50:44 -0600
> Organization: Memorial Sloan Kettering
> Keywords: 199405311941.AA11863

Hi Valerio,

> Here at Memorial Sloan Kettering, we have started to make rather intensive
> usage of the NetCDF format. All seems to work quite well, but we've found it
> necessary to make a few extensions. One in particular might be of interest
> to more users: ncinquire does not return the flags that were used to open
> the file, making it impossible to determine if a currently open file is in
> read-only or read/write mode.
> 
> I've added a simple function called ncopenmode. I've included the function
> in the CDF.C source and the prototype in the LOCAL_NC.H file. The call
> looks like this:
> 
>       ncopenmode(int cdfid, int *mode)
> 
> After using NC_check_id to verify the file, it simply returns the
> handle->flags value.

Thanks for the feedback.  This appears to be a gap in the current interface
that your proposed interface fills well.  We'll consider adding this to the
next version.

__________________________________________________________________________
                      
Russ Rew                                              UCAR Unidata Program
address@hidden                                        P.O. Box 3000
(303)497-8645                                 Boulder, Colorado 80307-3000