summaryrefslogtreecommitdiffstats
path: root/test/ttsafe.c
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r7109] Purpose:Quincey Koziol2003-06-261-1/+1
| | | | | | | | | | | Code cleanup Description: Clean up varios compiler warnings flagged by SGI compiler and gcc 3.3 Platforms tested: FreeBSD 4.8 (sleipnir) h5committest
* [svn-r6538] Purpose:Bill Wendling2003-03-311-11/+13
| | | | | | | | | | | | | Update Description: Updated the Copyright statement Platforms tested: Linux (This change is only in the comments, so I just check that the modules still compile) Misc. update:
* [svn-r4355] Purpose:Quincey Koziol2001-08-141-2/+2
| | | | | | | | | | | | | | | | | | | | | | Code cleanup (sorta) Description: When the first versions of the HDF5 library were designed, I remembered vividly the difficulties of porting code from a 32-bit platform to a 16-bit platform and asked that people use intn & uintn instead of int & unsigned int, respectively. However, in hindsight, this was overkill and unnecessary since we weren't going to be porting the HDF5 library to 16-bit architectures. Currently, the extra uintn & intn typedefs are causing problems for users who'd like to include both the HDF5 and HDF4 header files in one source module (like Kent's h4toh5 library). Solution: Changed the uintn & intn's to unsigned and int's respectively. Platforms tested: FreeBSD 4.4 (hawkwind)
* [svn-r3770] Purpose:Bill Wendling2001-04-031-1/+2
| | | | | | | | | | | | | | | | | Update Description: Changed includes of the form: #include <hdf5_file.h> to #include "hdf5_file.h" so that gcc can pick them up easier without including the system header files since we don't care about them. Platforms tested: Linux
* [svn-r3677] Purpose:Albert Cheng2001-03-201-4/+0
| | | | | | | | | | | | | Bug fix (sort of) Description: The RCSID string in H5public.h was causing the C++ code problem as it was included multiple times and C++ did not like multiple definitions of the same static variable. Solution: Since we don't really make use of the RCSID strings as we have not installed it in all source files, we decided to remove it. Platforms tested: eirene (linux), modi4 (IRIX64-64) both serial and parallel modes.
* [svn-r2533] Rolled back the changes I committed since Albert fixed the ↵Bill Wendling2000-09-111-4/+0
| | | | | | problem with FILENAME being extern global...
* [svn-r2532] Added a trivial FILENAME definition to those programs linked withBill Wendling2000-09-111-0/+4
| | | | h5test.o, which requires the definition to work...
* [svn-r2531] Description:Albert Cheng2000-09-101-4/+0
| | | | | | | | | | | | | | | | | | | The "FILENAME" declared extern in h5test.h is not always used. It was used in h5_cleanup to remove temporary files created during tests. Not all tests codes have used this routine. Indeed, quite a few of test programs do "#define FILENAME ". Also, h5_cleanup needs to work in tandem with h5_fixname. h5_fixname accepts an explicite base_name argument instead of using the global variable FILENAME. That is cleaner. Solution: Added char *base_name[] as a new argument to h5_cleanup, in the same style as h5_fixname. Removed "extern char *FILENAME..." from use. Also, undo some unnecessary declaration of "char *FILENAME" from some tests which don't use it at all (yet). Platforms tested: modi4-64(irix64), arabica(solari2.7), eirene(linux) (arabica could not launch tests automatically. I had to hack in LD_LIBRARY_PATH to make them run.)
* [svn-r2528] Linking errors occured with these files. They link with ↵Bill Wendling2000-09-081-1/+4
| | | | | | | libh5test, but libh5test wants FILENAME to be defined. I have no clue why this was working before...
* [svn-r2287] Changed ttsafe_* test files so that they create their own HDF5 ↵Bill Wendling2000-05-191-257/+274
| | | | | | | | file (they were only creating one for all of them). Also changed so that, if they got an error, it actually specifies that the tests failed on the screen instead of succeeded ;-)
* [svn-r2264] Added Thread-safe feature. This is the phase 1 implementationChee-Wai Lee2000-05-181-0/+334
that all HDF5 API functions are protected by a mutex lock. Basically, serialized all API calls. To use it, use configure --enable-threadsafe --with-pthread