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

Re: errno behavior

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: errno behavior
  • Date: Thu, 17 Feb 1994 16:22:43 -0700
> Keywords: 199402162046.AA22797

Hi Jim,

> I have been writing a rpc server for netcdf files and found the follwoing
> behavior WRT errno: When ncopts = NC_VERBOSE, errno is assigned 0 once the
> message is printed. I believe the line (157) in error.c
> 
>       errno = 0 ;             /* ??? */
> 
> should be
> 
>         errno = errnum;

Yes you're right.

> Also, When ncopts = 0 errno does not contain the correct error code. For
> example,
>        
>       id = ncopen("nothing", NC_NOWRITE);
> 
> where "nothing" does not exist should set errno to 2, but instead leaves the
> value unchanged.

We'll fix it for the next release.  Thanks for reporting the bug!

Also, several people have requested an RPC server for netcdf, and we had
actually planned to write one as well as part of another project that never
got funded.  Any chance you could make your server generally available?

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