Ignore:
Timestamp:
14/04/09 18:56:40 (3 years ago)
Author:
Freddie Akeroyd
Message:

Merg in r1212:r1222 from trunk. Refs #115.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/4.2/src/napi.c

    r1104 r1230  
    3535#include "napi.h" 
    3636#include "nxstack.h" 
     37 
     38/** 
     39 * \mainpage NeXus API documentation 
     40 * \section sec_purpose Purpose of API 
     41 * The NeXus Application Program Interface is a suite of subroutines, written in C but with wrappers in Fortran 77 and 90.  
     42 *  The subroutines call HDF routines to read and write the NeXus files with the correct structure.  
     43 * An API serves a number of useful purposes:  
     44 * - It simplifies the reading and writing of NeXus files.  
     45 * - It ensures a certain degree of compliance with the NeXus standard.  
     46 * - It allows the development of sophisticated input/output features such as automatic unit conversion. This has not been implemented yet.  
     47 * - It hides the implementation details of the format. In particular, the API can read and write HDF4,  
     48     HDF5 (and shortly XML) files using the same routines.  
     49 * For these reasons, we request that all NeXus files are written using the supplied API. We cannot be  
     50 * sure that anything written using the underlying HDF API will be recognized by NeXus-aware utilities.  
     51 * 
     52 * \section sec_core Core API 
     53 * The core API provides the basic routines for reading, writing and navigating NeXus files. It is designed to be modal;  
     54 * there is a hidden state that determines which groups and data sets are open at any given moment, and  
     55 * subsequent operations are implicitly performed on these entities. This cuts down the number of parameters  
     56 * to pass around in API calls, at the cost of forcing a certain pre-approved mode d'emploi. This mode d'emploi  
     57 * will be familiar to most: it is very similar to navigating a directory hierarchy; in our case, NeXus groups are the  
     58 * directories, which contain data sets and/or other directories.  
     59 * 
     60 * The core API comprises several functional groups which are listed on the \b Modules tab  
     61 * 
     62 * C programs that call the above routines should include the following header file:  
     63 * \code 
     64 * #include "napi.h" 
     65 * \endcode 
     66 */ 
     67 
     68 
    3769 
    3870/*--------------------------------------------------------------------- 
     
    825857    return status; 
    826858  } 
    827      
     859/*---------------------------------------------------------------------------*/ 
     860  NXstatus  NXgetrawinfo (NXhandle fid, int *rank,  
     861                                    int dimension[], int *iType) 
     862  { 
     863    int status; 
     864    char *pPtr = NULL; 
     865 
     866    pNexusFunction pFunc = handleToNexusFunc(fid); 
     867    status = pFunc->nxgetinfo(pFunc->pNexusData, rank, dimension, iType); 
     868    return status; 
     869  } 
    828870  /*-------------------------------------------------------------------------*/ 
    829871  
Note: See TracChangeset for help on using the changeset viewer.