all functions - y

             yhd_check(file);  
 
       -or- yhd_check(file, version, date, encoding, comment);  
     Return 1 (true) if FILE is a valid YHD file; otherwise return 0  
     (false).  The nature of FILE is guessed by reading its header.  Input  
     argument FILE can be a file name (scalar string) of a binary file  
     stream opened for reading; all other arguments are pure outputs and  
     may be omitted (if result is false, the contents of these outputs is  
     undetermined).  
interpreted function, defined at contrib/yeti_yhdf.i   line 273  

             yhd_info, file;  
 
     Print out some information about YHD file.  FILE can be a file  
     name (scalar string) of a binary file stream opened for reading.  
interpreted function, defined at contrib/yeti_yhdf.i   line 315  

             yhd_restore(filename);  
 
       -or- yhd_restore(filename, keylist, ...);  
     Restore and return hash table object saved in YHD file FILENAME.  If  
     additional arguments are provided, they are the names of members to  
     restore.  The default is to restore every member.  
interpreted function, defined at contrib/yeti_yhdf.i   line 331  

             yhd_save, filename, obj;  
 
       -or- yhd_save, filename, obj, keylist, ...;  
     Save contents of hash object OBJ into the Yeti Hierarchical Data (YHD)  
     file FILENAME.  If additional arguments are provided, they are the  
     names of members to save.  The default is to save every member.  
     Keyword COMMENT can be used to store a (short) string comment in the  
     file header.  The comment is truncated if it is too long (more than  
     about 130 bytes) to fit into the header.  COMMENT must not contain  
     any DEL (octal 177) character.  
     Keyword ENCODING can be used to specify a particular binary data  
     format for the file; ENCODING can be the name of some known data  
     format (see get_encoding) or an array of 32 integers (see  
     set_primitives).  The default is to use the native data format.  
     If keyword OVERWRITE is true and file FILENAME already exists, the new  
     file will (silently) overwrite the old one; othwerwise, file FILENAME  
     must not already exists (defalut behaviour).  
interpreted function, defined at contrib/yeti_yhdf.i   line 34  

             ylm_coef(l,m)  
 
     return sqrt((2*l+1)(l-m)!/(4*pi*(l+m)!)), the normalization  
     coefficient for spherical harmonic Ylm with respect to the  
     associated Legendre function Plm.  In this implementation,  
     0<=m<=l; use symmetry for m<0, or use sines and cosines  
     instead of complex exponentials.  Unlike Plm, array L and M  
     arguments are permissible here.  
     WARNING: These get combinitorially small with large L and M;  
     probably Plm is simultaneously blowing up and should be  
     normalized directly in legndr if what you want is Ylm.  But  
     I don't feel like working all that out -- if you need large  
     L and M results, you should probably be working with some  
     sort of asymptotic form anyway...  
interpreted function, defined at i/legndr.i   line 55  

 ylm_test  
 
  
interpreted function, defined at i/ylmdec.i   line 61  

 yorick_init  
 
  
builtin function, documented at i0/std.i   line 211  

             yorick_stats  
 
     returns an array of longs describing Yorick memory usage.  
     For debugging.  See ydata.c source code.  
builtin function, documented at i0/std.i   line 247