James Laird 5c0011a713 [svn-r9329]
Purpose:
Feature

Description:
Datatypes and groups now use H5FO "file object" code that was previously
only used by datasets.  These objects will hold a file open if the file
is closed but they have not yet been closed.  If these objects are unlinked
then relinked, they will not be destroyed.  If they are opened twice (even
by two different names), both IDs will "see" changes made to the object
using the other ID.
When an object is opened using two different names (e.g., if a dataset was
opened under one name, then mounted and opened under its new name), calling
H5Iget_name() on a given hid_t will return the name used to open that hid_t,
not the current name of the object (this is a feature, and a change from the
previous behavior of datasets).

Solution:
Used H5FO code that was already in place for datasets.  Broke H5D_t's, H5T_t's,
and H5G_t's into a "shared" struct and a private struct.  The shared structs
(H5D_shared_t, etc.) hold the object's information and are used by all IDs
that point to a given object in the file.  The private structs are pointed
to by the hid_t and contain the object's group entry information (including its
name) and a pointer to the shared struct for that object.
This changed the naming of structs throughout the library (e.g., datatype->size
is now datatype->shared->size).  I added an updated H5Tinit.c to windows.zip.

Platforms tested:
Visual Studio 7, sleipnir, arabica, verbena

Misc. update:
2004-09-28 14:04:19 -05:00
2004-09-25 16:48:51 -05:00
2004-09-08 21:37:02 -05:00
2004-09-07 16:38:49 -05:00
2004-08-16 17:49:03 -05:00
2004-09-14 00:04:25 -05:00
2003-08-13 23:58:29 -05:00
2003-08-27 12:04:21 -05:00
2004-09-01 12:43:30 -05:00
2004-09-27 23:34:38 -05:00
2004-09-28 14:04:19 -05:00
2004-09-28 14:04:19 -05:00
2004-09-24 16:20:24 -05:00
2004-09-28 14:04:19 -05:00
2004-09-28 14:04:19 -05:00
2003-02-06 17:06:35 -05:00
2003-06-28 00:14:02 -05:00
2003-08-04 10:30:54 -05:00
2004-02-10 18:01:33 -05:00
2003-08-13 23:58:29 -05:00
2004-08-23 13:43:22 -05:00

HDF5 version 1.7.39 currently under development
Please refer to the release_docs/INSTALL file for installation instructions.
------------------------------------------------------------------------------

This release is almost fully functional for the entire API defined in the
documentation, see the RELEASE.txt file in this directory for information
specific to this release of the library.  The INSTALL file contains
instructions on compiling and installing the library.  The INSTALL_parallel
file contains instructions on installing the parallel version of the
library.  The INSTALL* files can be found in the release_docs/ directory.

Documentation for this release is in the html directory.  Start with the
"index.html" in that directory.

Four mailing lists are currently set up for use with the HDF5
library.

   hdf5         - For general discussion of the HDF5 library with
		  other users.

   hdf5dev      - For discussion of the HDF5 library development
		  with developers and other interested parties.

   hdf5announce - For announcements of HDF5 related developments,
		  not a discussion list.

   hdf5cvs      - For checkin notices of code development on the library,
		  not a discussion list.

To subscribe to a list, send mail to "majordomo@ncsa.uiuc.edu",
with "subscribe <list>" in the _body_, not the Subject, of the message.
E.g., subscribe hdf5 

Messages to be sent to the list should be sent to "<list>@ncsa.uiuc.edu".

Nearly daily code snapshots are now being provided at the following URL:
    ftp://hdf.ncsa.uiuc.edu/pub/outgoing/hdf5/snapshots
Please read the readme file in that directory before working with a library
snapshot.

The HDF5 website is located at http://hdf.ncsa.uiuc.edu/HDF5/

Bugs should be reported to hdfhelp@ncsa.uiuc.edu.
Description
No description provided
Readme 616 MiB
Languages
C 81.7%
Fortran 4.5%
Java 4%
CMake 3.3%
C++ 2.5%
Other 3.9%