Thread: [Getdata-commits] SF.net SVN: getdata:[698] trunk/getdata/NEWS
Scientific Database Format
Brought to you by:
ketiltrout
Menu
▾
▴
getdata-commits
|
From: <ket...@us...> - 2012-04-06 16:18:25
|
Revision: 698
http://getdata.svn.sourceforge.net/getdata/?rev=698&view=rev
Author: ketiltrout
Date: 2012-04-06 16:18:19 +0000 (Fri, 06 Apr 2012)
Log Message:
-----------
NEWS
Modified Paths:
--------------
trunk/getdata/NEWS
Modified: trunk/getdata/NEWS
===================================================================
--- trunk/getdata/NEWS 2012-04-06 16:17:12 UTC (rev 697)
+++ trunk/getdata/NEWS 2012-04-06 16:18:19 UTC (rev 698)
@@ -112,7 +112,8 @@
metadata on open.
* BUG FIX: GetData no longer omits the input field to a RECIP when writing
- metadata to disk.
+ metadata to disk. Nor does it forget to put newlines after RECIP or DIVIDE
+ field specifications.
* BUG FIX: GetData no longer assumes all fields have the same number of
samples-per-frame when computing a LINCOM.
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ket...@us...> - 2013-11-15 22:01:44
|
Revision: 865
http://sourceforge.net/p/getdata/code/865
Author: ketiltrout
Date: 2013-11-15 22:01:40 +0000 (Fri, 15 Nov 2013)
Log Message:
-----------
typo
Modified Paths:
--------------
trunk/getdata/NEWS
Modified: trunk/getdata/NEWS
===================================================================
--- trunk/getdata/NEWS 2013-11-13 21:56:54 UTC (rev 864)
+++ trunk/getdata/NEWS 2013-11-15 22:01:40 UTC (rev 865)
@@ -4,8 +4,9 @@
* The gd_free_entry_strings() function now NULLs pointers after freeing them.
- * The gd_[m]add() functions now ignore zero-length scalar strings. Previously
- they would store these invalid field codes, causing problems later.
+ * BUG FIX: The gd_[m]add() functions now ignore zero-length scalar strings.
+ Previously they would store these invalid field codes, causing problems
+ later.
* BUG FIX: Returning complex-valued CARRAYs as purely real now works.
Previously only the first element requested would be returned, the remaining
@@ -58,7 +59,7 @@
* F95 BUG FIX: fgd_add and fgd_alter_entry no longer ignore named scalar
parameters provided in supplied entry structures.
- * C++ BUG FIX: Fixed segfault in RawEntry distructor. Reported by S. J.
+ * C++ BUG FIX: Fixed segfault in RawEntry destructor. Reported by S. J.
Benton.
|==============================================================================|
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ket...@us...> - 2014-12-14 03:50:10
|
Revision: 938
http://sourceforge.net/p/getdata/code/938
Author: ketiltrout
Date: 2014-12-14 03:50:00 +0000 (Sun, 14 Dec 2014)
Log Message:
-----------
Update for bugfixes backported to 0.8.6.
Modified Paths:
--------------
trunk/getdata/NEWS
Modified: trunk/getdata/NEWS
===================================================================
--- trunk/getdata/NEWS 2014-12-07 05:27:01 UTC (rev 937)
+++ trunk/getdata/NEWS 2014-12-14 03:50:00 UTC (rev 938)
@@ -30,10 +30,10 @@
gzip-encoded data works. See the gzip discussion in the 0.8.0 section below
for important notes.
- * A newly-created dirfile is now always opened in read-write mode, ignoring the
- access mode specified in the call. Previously, specifying both GD_RDONLY and
- GD_CREAT in open calls would result in an access mode (GD_E_ACCMODE) error if
- the dirfile didn't already exist.
+ * A newly-created dirfile is now always opened in read-write mode, ignoring
+ the access mode specified in the call. Previously, specifying both
+ GD_RDONLY and GD_CREAT in open calls would result in an access mode
+ (GD_E_ACCMODE) error if the dirfile didn't already exist.
* BUG FIX: In addition to the addition of write support mentioned above, a
number of problems with reading LZMA files has been fixed, which should
@@ -44,8 +44,6 @@
interpreted as a simple field code (which may be rejected later due to the
presence of the invalid '<' character).
- * BUG FIX: The parsing of the \x and \u escape sequences is now correct.
-
* BUG FIX: The parser no-longer interprets various numbers as field codes
when it shouldn't (e.g. when specifying a PHASE shift as "1." instead of
"1").
@@ -64,10 +62,6 @@
represented in the metadata on disk. For the behaviour with later Versions,
and in permissive mode, see the previous.
- * BUG FIX: Computation of LINCOMs with complex valued input fields now
- correctly happens in the complex plane. As a side effect, gd_native_type()
- now also correctly reports such LINCOM fields to be complex valued.
-
* BUG FIX: If performing a metadata update due to renaming fields (perhaps
by passing GD_REN_UPDB to gd_rename()) results in an invalid field code
due to affix restrictions, the update now fails (but see GD_REN_FORCE).
@@ -78,65 +72,13 @@
codes containing subfields of the renamed field are now also updated,
including field codes specifying meta subfields which do not exist.
- * BUG FIX: The gd_[m]add() functions now ignore zero-length strings in the
- scalar[] member (i.e., they treat them as if they were NULL). Previously
- they would store these invalid field codes, causing problems later.
-
- * BUG FIX: Fetching complex-valued CARRAYs as purely real data now works.
- Previously only the first element requested would be returned, the remaining
- output buffer containing uninitialised data.
-
- * BUG FIX: A scalar field code specified for the last factor in a POLYNOM
- entry is no longer ignored by gd_[m]add().
-
- * BUG FIX: Entry members spf, bitnum, numbits, and period are now completely
- ignored by gd_[m]add() if corresponding named scalars are specified.
- Previously, an invalid value in these members would result in the entry
- being rejected, even though the invalid value was immediately discarded
- when the field was added.
-
- * BUG FIX: gd_[m]add() no longer rejects MPLEX fields with negative count_val.
-
- * BUG FIX: gd_alter_entry() no longer corrupts the DIRFILE when modifying
- named scalars of MPLEX fields.
-
* BUG FIX: reading a LINTERP table with fewer than two lines no longer results
in a segfault on close/discard.
- * BUG FIX: DIVIDE fields with complex-valued divisors are now properly
- computed.
-
- * BUG FIX: Complex-valued DIVIDE, POLYNOM, and RECIP fields are now computed
- properly when the library is built in ANSI C mode.
-
- * BUG FIX: Writing complex-valued MPLEX fields no longer corrupts the stored
- data.
-
* BUG FIX: Several fixes have been made to the sample index encoding (SIE)
engine, which should now produce properly encoded data when performing
random writes.
- * BUG FIX: gd_bof() now returns the correct number (i.e.: zero) when reporting
- the beginning of field of derived fields shifted to before the start of the
- dirfile. Previously, this function incorrectly returned values ranging from
- zero to one less than the samples-per-frame of the requested field.
-
- * BUG FIX: gd_flush(), gd_sync(), gd_raw_close() no longer segfault when
- operating on a LINCOM with only one input field.
-
- * BUG FIX: gd_seek() now works correctly on PHASE fields; previously, the
- sign of the PHASE shift was flipped.
-
- * BUG FIX: gd_seek() now correctly positions the virtual I/O pointer of the
- INDEX field.
-
- * BUG FIX: gd_framenum_subset() now returns the correct value when passed a
- field_end which is beyond the end of field, and then is required to
- extrapolate outside of the specified frame range.
-
- * BUG FIX: gd_error_string() now produces the correct string when reporting
- an out-of-range poly_ord encountered by gd_add_polynom() and similar.
-
* BUG FIX: gd_alter_raw() and similar no longer fail when asked to re-encode
the data file of a RAW field which has not been previously accessed.
@@ -145,19 +87,6 @@
obsolete, cached LUTs would sometimes linger, causing incorrect LINTERP
computation.
- * BUG FIX: gd_[m]alter_spec() no longer ignore co-efficients specified for
- POLYNOM entries.
-
- * BUG FIX: gd_alter_encoding() now deletes the internal cache of RAW filenames
- of the affected fragment; previously, these old, cached filenames could lead
- to I/O errors when reading and writing the re-encoded RAW data files.
-
- * BUG FIX: Calling the Legacy API function GetFormat() on a Dirfile with MPLEX
- or WINDOW fields no longer results in a segmentation fault.
-
- * BUG FIX: Attempts to read past the EOF of a gzipped field no longer results
- in an I/O error, but successfully returns no data.
-
API Changes:
* CLARIFICATION: The macro GD_SIZE() declared in getdata.h is indeed part of
@@ -198,11 +127,11 @@
alias points to.
* A number of different error codes which indicated the same problem (an
- I/O error returned by the filesystem) have been merged into one. The error
- codes GD_E_OPEN, GD_E_TRUNC, GD_E_RAW_IO, GD_E_OPEN_FRAGMENT, GD_E_FLUSH
- are replaced by the new error GD_E_IO. The old symbols remain as aliases
- but are deprecated. There is one exception to this merge: attempts to
- flush metadata lines which are too long are now reported using
+ I/O error returned by the operating system) have been merged into one. The
+ error codes GD_E_OPEN, GD_E_TRUNC, GD_E_RAW_IO, GD_E_OPEN_FRAGMENT,
+ GD_E_FLUSH are replaced by the new error GD_E_IO. The old symbols remain as
+ aliases but are deprecated. There is one exception to this merge: attempts
+ to flush metadata lines which are too long are now reported using
GD_E_LINE_TOO_LONG. Previously, these errors used GD_E_FLUSH.
* The error code GD_E_OPEN_LINFILE has also been removed. It has been split
@@ -260,25 +189,9 @@
error codes (such as OpenError). These deprecated exceptions are simply
aliases for the current ones and are never returned by the bindings.
- * C++ BUG FIX: Fixed segfault in RawEntry destructor. Reported by S. J.
- Benton.
-
- * C++ BUG FIX: Entry::ComplexScalars() now returns non-zero for RECIP
- entries when appropriate, instead of always returning zero. (The
- RecipEntry::ComplexScalars() method always returned the correct value.)
-
- * F77 and F95 BUG FIX: Named scalar indices are now indexed from one instead
- of zero, like all other array indices are in the Fortran GetData bindings.
-
* F95 BUG FIX: fgd_add and fgd_alter_entry no longer ignore named scalar
parameters provided in supplied entry structures.
- * IDL BUG FIX: the /UPDATEDB flag to gd_rename now operates as expected.
- Previously it would act like /MOVE_DATA.
-
- * PYTHON BUG FIX: The keyword for the "dirfile" parameter in the
- getdata.fragment constructor is now properly spelled.
-
Miscellaneous:
* The minimum autotools versions have been bumped. Autoconf-2.65 or newer,
@@ -291,6 +204,104 @@
|==============================================================================|
+New in version 0.8.6:
+
+ Library Changes:
+
+ * BUG FIX: Computation of LINCOMs with complex valued input fields now
+ correctly happens in the complex plane. As a side effect, gd_native_type()
+ now also correctly reports such LINCOM fields to be complex valued.
+
+ * BUG FIX: The gd_[m]add() functions now ignore zero-length scalar strings.
+ Previously they would store these invalid field codes, causing problems
+ later.
+
+ * BUG FIX: Returning complex-valued CARRAYs as purely real now works.
+ Previously only the first element requested would be returned, the remaining
+ output buffer containing uninitialised data.
+
+ * BUG FIX: Entry members spf, bitnum, numbits, and period are now completely
+ ignored by gd_[m]add() when corresponding named scalars are specified.
+ Previously, an invalid value in these members would result in the entry
+ being rejected, even though the rest of GetData ignored the invalid, unsued
+ value.
+
+ * BUG FIX: The parsing of the \x and \u escape sequences is now correct.
+
+ * BUG FIX: A scalar field code specified for the last factor in a POLYNOM
+ entry is no longer ignored by gd_[m]add().
+
+ * BUG FIX: gd_[m]add() no longer rejects MPLEX fields with negative count_val.
+
+ * BUG FIX: DIVIDE fields with complex-valued divisors are now properly
+ computed.
+
+ * BUG FIX: Complex-valued POLYNOM and RECIP fields are now computed properly
+ when the library is built in ANSI C mode.
+
+ * BUG FIX: gd_alter_entry() no longer corrupts the DIRFILE when modifying
+ named scalars of MPLEX fields.
+
+ * BUG FIX: Writing complex-valued MPLEX fields no longer corrupts the stored
+ data.
+
+ * BUG FIX: gd_bof() now returns the correct number (i.e.: zero) when reporting
+ the beginning of field of derived fields shifted to before the start of the
+ dirfile. Previously, this function incorrectly returned values ranging from
+ zero to one less than the samples-per-frame of the requested field.
+
+ * BUG FIX: gd_flush(), gd_sync(), gd_raw_close() no longer segfault when
+ operating on a LINCOM with only one input field.
+ * BUG FIX: gd_seek() now works correctly on PHASE fields; previously, the
+ sign of the PHASE shift was flipped.
+
+ * BUG FIX: gd_seek() now correctly positions the virtual I/O pointer of the
+ INDEX field.
+
+ * BUG FIX: gd_framenum_subset() now returns the correct value when passed a
+ field_end which is beyond the end of field, and then is required to
+ extrapolate outside of the specified frame range.
+
+ * BUG FIX: gd_error_string() now produces the correct string when reporting
+ an out-of-range poly_ord encountered by gd_add_polynom() and similar.
+
+ * BUG FIX: gd_[m]alter_spec() no longer ignore co-efficients specified for
+ POLYNOM entries.
+
+ * BUG FIX: gd_alter_encoding() now deletes the internal cache of RAW filenames
+ of the affected fragment; previously, these old, cached filenames could lead
+ to I/O errors when reading and writing the re-encoded RAW data files.
+
+ * BUG FIX: Calling the Legacy API function GetFormat() on a Dirfile with MPLEX
+ or WINDOW fields no longer results in a segmentation fault.
+
+ * BUG FIX: Attempts to read past the EOF of a gzipped field no longer results
+ in an I/O error, but successfully returns no data.
+
+ * BUG FIX: The internal recursion counter wasn't being properly reset on
+ certain error conditions, leading to spurious GD_E_RECURSE_LEVEL errors
+ being returned from valid calls.
+
+ Bindings Changes:
+
+ * F77 and F95 BUG FIX: Named scalar indices are now indexed from one instead
+ of zero, like all other array indices are in the Fortran GetData bindings.
+
+ * C++ BUG FIX: Fixed segfault in RawEntry destructor. Reported by S. J.
+ Benton.
+
+ * C++ BUG FIX: Entry::ComplexScalars() now returns non-zero for RECIP
+ entries when appropriate, instead of always returning zero. (The
+ RecipEntry::ComplexScalars() method always returned the correct value.)
+
+ * IDL BUG FIX: The /UPDATEDB flag to gd_rename is no longer ignored; also, the
+ /MOVE_DATA flag no longer also acts as if /UPDATEDB had been specified.
+
+ * PYTHON BUG FIX: The keyword for the "dirfile" parameter in the
+ getdata.fragment constructor is now properly spelled.
+
+|==============================================================================|
+
New in verison 0.8.5:
Library Changes:
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ket...@us...> - 2015-04-03 01:53:39
|
Revision: 946
http://sourceforge.net/p/getdata/code/946
Author: ketiltrout
Date: 2015-04-03 01:53:26 +0000 (Fri, 03 Apr 2015)
Log Message:
-----------
Reformat with linewidth=75
Modified Paths:
--------------
trunk/getdata/NEWS
Modified: trunk/getdata/NEWS
===================================================================
--- trunk/getdata/NEWS 2015-04-03 00:14:27 UTC (rev 945)
+++ trunk/getdata/NEWS 2015-04-03 01:53:26 UTC (rev 946)
@@ -3,161 +3,169 @@
Library Changes:
* Literals in format metadata may now have complex form (i.e. include a
- semicolon) when the parameter is purely real. However, a non-zero imaginary
- part is still an error.
+ semicolon) when the parameter is purely real. However, a non-zero
+ imaginary part is still an error.
* gd_free_entry_strings() now NULLs pointers after freeing them.
- * gd_entry() now returns entry metadata when they contain scalar field codes
- which do not exist. In this case the GD_EN_CALC flag in the object will
- not be set. Previously, on such entries, this function would fail with the
- error GD_E_BAD_SCALAR, and return nothing.
+ * gd_entry() now returns entry metadata when they contain scalar field
+ codes which do not exist. In this case the GD_EN_CALC flag in the
+ object will not be set. Previously, on such entries, this function
+ would fail with the error GD_E_BAD_SCALAR, and return nothing.
* gd_rename() now by default updates the target of ALIASes pointing to a
renamed field to point to the new field instead of leaving them dangle.
(But see GD_REN_DANGLE in the API section below).
- * CARRAYs are no longer truncated to GD_MAX_CARRAY_LENGTH elements. Flushing
- metadata to disk will now fail if writing a CARRAY would overflow a format
- file line. (It's platform specific, but format file lines are typically
- permitted to be at least 2**31 bytes long, so such an error usually
- indicates something pathological happening.) The GD_MAX_CARRAY_LENGTH
- symbol has been removed from the GetData header file.
+ * CARRAYs are no longer truncated to GD_MAX_CARRAY_LENGTH elements.
+ Flushing metadata to disk will now fail if writing a CARRAY would
+ overflow a format file line. (It's platform specific, but format file
+ lines are typically permitted to be at least 2**31 bytes long, so such
+ an error usually indicates something pathological happening.) The
+ GD_MAX_CARRAY_LENGTH symbol has been removed from the GetData header
+ file.
- * Write support for bzip2-encoded and lzma-encoded data has been added. LZMA
- write support is only available for .xz files, not the obsolete .lzma
- format. The write support occurs out-of-place, just like how writing
- gzip-encoded data works. See the gzip discussion in the 0.8.0 section below
- for important notes.
+ * Write support for bzip2-encoded and lzma-encoded data has been added.
+ LZMA write support is only available for .xz files, not the obsolete
+ .lzma format. The write support occurs out-of-place, just like how
+ writing gzip-encoded data works. See the gzip discussion in the 0.8.0
+ section below for important notes.
- * A newly-created dirfile is now always opened in read-write mode, ignoring
- the access mode specified in the call. Previously, specifying both
+ * A newly-created dirfile is now always opened in read-write mode, ignor-
+ ing the access mode specified in the call. Previously, specifying both
GD_RDONLY and GD_CREAT in open calls would result in an access mode
(GD_E_ACCMODE) error if the dirfile didn't already exist.
* Many functions which used to silently ignore representation suffixes in
- field codes passed to them no longer do that. Most of these will report
- an error (GD_E_BAD_CODE) if passed a representation suffix. The affected
- functions are: gd_bof, gd_entry, gd_entry_type, gd_eof, gd_flush,
- gd_linterp_tablename, gd_put_carray, gd_put_carray_slice, gd_putdata,
- gd_raw_close, gd_raw_filename, gd_seek, gd_spf, gd_sync, gd_tell.
+ field codes passed to them no longer do that. Most of these will
+ report an error (GD_E_BAD_CODE) if passed a representation suffix. The
+ affected functions are: gd_bof, gd_entry, gd_entry_type, gd_eof,
+ gd_flush, gd_linterp_tablename, gd_put_carray, gd_put_carray_slice,
+ gd_putdata, gd_raw_close, gd_raw_filename, gd_seek, gd_spf, gd_sync,
+ gd_tell.
- * BUG FIX: In addition to the addition of write support mentioned above, a
- number of problems with reading LZMA files has been fixed, which should
- result in fewer segmentaion faults.
+ * BUG FIX: In addition to the addition of write support mentioned above,
+ a number of problems with reading LZMA files has been fixed, which
+ should result in fewer segmentaion faults.
- * BUG FIX: The parser no longer silently appends a closing > to scalar field
- codes that contain an umatched opening < (e.g. "scalar<3"). This is now
- interpreted as a simple field code (which may be rejected later due to the
- presence of the invalid '<' character).
+ * BUG FIX: The parser no longer silently appends a closing > to scalar
+ field codes that contain an umatched opening < (e.g. "scalar<3"). This
+ is now interpreted as a simple field code (which may be rejected later
+ due to the presence of the invalid '<' character).
* BUG FIX: The parser no-longer interprets various numbers as field codes
- when it shouldn't (e.g. when specifying a PHASE shift as "1." instead of
- "1").
+ when it shouldn't (e.g. when specifying a PHASE shift as "1." instead
+ of "1").
- * BUG FIX: When writing scalar field codes to disk which could be interpreted
- as a number (e.g. the field code "1"), the library now forces the
- interpretation of these field codes as codes rather than numbers by
+ * BUG FIX: When writing scalar field codes to disk which could be inter-
+ preted as a number (e.g. the field code "1"), the library now forces
+ the interpretation of these field codes as codes rather than numbers by
appending a scalar index (making, e.g., "1<0>"), which is harmless.
- Previously, these were written as-is, resulting in misinterpretation the
- next time the Dirfile was opened. This only happens with Standards Version
- 8 or later, see the following for earlier versions.
+ Previously, these were written as-is, resulting in misinterpretation
+ the next time the Dirfile was opened. This only happens with Standards
+ Version 8 or later, see the following for earlier versions.
* BUG FIX: If the current Standards Version in effect is 7 or earlier,
ambiguous field codes (e.g., "1"), are now rejected by gd_[m]add() and
gd_alter_entry() with the error GD_E_BAD_CODE, since they can't be
- represented in the metadata on disk. For the behaviour with later Versions,
- and in permissive mode, see the previous.
+ represented in the metadata on disk. For the behaviour with later
+ Versions, and in permissive mode, see the previous.
- * BUG FIX: If performing a metadata update due to renaming fields (perhaps
- by passing GD_REN_UPDB to gd_rename()) results in an invalid field code
- due to affix restrictions, the update now fails (but see GD_REN_FORCE).
- Previously the invalid field code would be stored, leading to errors when
- flushing the modified metadata to disk.
+ * BUG FIX: If performing a metadata update due to renaming fields
+ (perhaps by passing GD_REN_UPDB to gd_rename()) results in an invalid
+ field code due to affix restrictions, the update now fails (but see
+ GD_REN_FORCE). Previously the invalid field code would be stored,
+ leading to errors when flushing the modified metadata to disk.
- * BUG FIX: When performing a metadata update due to a renamed field, the field
- codes containing subfields of the renamed field are now also updated,
- including field codes specifying meta subfields which do not exist.
+ * BUG FIX: When performing a metadata update due to a renamed field, the
+ field codes containing subfields of the renamed field are now also
+ updated, including field codes specifying meta subfields which do not
+ exist.
- * BUG FIX: reading a LINTERP table with fewer than two lines no longer results
- in a segfault on close/discard.
+ * BUG FIX: reading a LINTERP table with fewer than two lines no longer
+ results in a segfault on close/discard.
- * BUG FIX: Several fixes have been made to the sample index encoding (SIE)
- engine, which should now produce properly encoded data when performing
- random writes.
+ * BUG FIX: Several fixes have been made to the sample index encoding
+ (SIE) engine, which should now produce properly encoded data when
+ performing random writes.
- * BUG FIX: gd_alter_raw() and similar no longer fail when asked to re-encode
- the data file of a RAW field which has not been previously accessed.
+ * BUG FIX: gd_alter_raw() and similar no longer fail when asked to re-
+ encode the data file of a RAW field which has not been previously
+ accessed.
* BUG FIX: A previously-read LINTERP table is now always discarded when
- changing table paths with gd_alter_linterp() or similar. Previously these
- obsolete, cached LUTs would sometimes linger, causing incorrect LINTERP
- computation.
+ changing table paths with gd_alter_linterp() or similar. Previously
+ these obsolete, cached LUTs would sometimes linger, causing incorrect
+ LINTERP computation.
API Changes:
- * CLARIFICATION: The macro GD_SIZE() declared in getdata.h is indeed part of
- the public API. It returns the size in bytes of a sample of data of a given
- type (e.g. GD_SIZE(GD_COMPLEX64) returns 8). It has been around since
- GetData-0.3.0, but has only been documented since GetData-0.8.3.
+ * CLARIFICATION: The macro GD_SIZE() declared in getdata.h is indeed part
+ of the public API. It returns the size in bytes of a sample of data of
+ a given type (e.g. GD_SIZE(GD_COMPLEX64) returns 8). It has been
+ around since GetData-0.3.0, but has only been documented since
+ GetData-0.8.3.
* A new data type code, GD_STRING, has been declared. It is needed in
- gd_getdata() calls to retrieve SINDIR data. Purely for convenience, it has
- the property: GD_SIZE(GD_STRING) == sizeof(char*).
+ gd_getdata() calls to retrieve SINDIR data. Purely for convenience, it
+ has the property: GD_SIZE(GD_STRING) == sizeof(char*).
* get_native_type() now returns GD_STRING for string type fields (STRING,
SARRAY, SINDIR). Formerly it would return GD_NULL.
- * The comp_scal member of the gd_entry_t object has been replaced with a flags
- member, containing a flag (GD_EN_COMPSCAL) with the meaning of the former
- comp_scal member. There are also flags for hiddenness (GD_EN_HIDDEN) and
- whether the scalar entry codes in the field definition have been
- dereferenced (GD_EN_CALC).
+ * The comp_scal member of the gd_entry_t object has been replaced with a
+ flags member, containing a flag (GD_EN_COMPSCAL) with the meaning of
+ the former comp_scal member. There are also flags for hiddenness
+ (GD_EN_HIDDEN) and whether the scalar entry codes in the field defi-
+ nition have been dereferenced (GD_EN_CALC).
* gd_[m]add() and gd_alter_entry() can now be used to set or change the
- hiddenness of a field by setting or clearing the GD_EN_HIDDEN bit in the
- supplied gd_entry_t object.
+ hiddenness of a field by setting or clearing the GD_EN_HIDDEN bit in
+ the supplied gd_entry_t object.
* Two new rename flags have been added:
- - GD_REN_DANGLE which indicates the library shouldn't update ALIASes whose
- target has been renamed (instead it will turn them into dangling aliases)
- - GD_REN_FORCE which causes the library to skip updating field codes which
- would be invalid due to affixes instead of failing.
+ - GD_REN_DANGLE which indicates the library shouldn't update ALIASes
+ whose target has been renamed (instead it will turn them into
+ dangling aliases)
+ - GD_REN_FORCE which causes the library to skip updating field codes
+ which would be invalid due to affixes instead of failing.
- * The move_data argument of gd_move() has been replaced with a flags argument
- which accepts the GD_REN_* flags, which have the same meaning as they do
- with gd_rename().
+ * The move_data argument of gd_move() has been replaced with a flags
+ argument which accepts the GD_REN_* flags, which have the same meaning
+ as they do with gd_rename().
- * gd_move_alias() and gd_delete_alias() have been deleted: their functions are
- now performed by gd_move() and gd_delete(), which now operate on the alias
- itself when given the field code to an alias, rather than the field the
- alias points to.
+ * gd_move_alias() and gd_delete_alias() have been deleted: their
+ functions are now performed by gd_move() and gd_delete(), which now
+ operate on the alias itself when given the field code to an alias,
+ rather than the field the alias points to.
* A number of different error codes which indicated the same problem (an
- I/O error returned by the operating system) have been merged into one. The
- error codes GD_E_OPEN, GD_E_TRUNC, GD_E_RAW_IO, GD_E_OPEN_FRAGMENT,
- GD_E_FLUSH are replaced by the new error GD_E_IO. The old symbols remain as
- aliases but are deprecated. There is one exception to this merge: attempts
- to flush metadata lines which are too long are now reported using
- GD_E_LINE_TOO_LONG. Previously, these errors used GD_E_FLUSH.
+ I/O error returned by the operating system) have been merged into one.
+ The error codes GD_E_OPEN, GD_E_TRUNC, GD_E_RAW_IO, GD_E_OPEN_FRAGMENT,
+ GD_E_FLUSH are replaced by the new error GD_E_IO. The old symbols
+ remain as aliases but are deprecated. There is one exception to this
+ merge: attempts to flush metadata lines which are too long are now
+ reported using GD_E_LINE_TOO_LONG. Previously, these errors used
+ GD_E_FLUSH.
- * The error code GD_E_OPEN_LINFILE has also been removed. It has been split
- into two parts:
- - I/O errors resulting from reading the LINTERP table file are now reported
- using GD_E_IO;
- - Syntax errors in the table are reported using the new GD_E_LUT error code.
- GD_E_OPEN_LINFILE remains as a deprecated alias for GD_E_LUT.
+ * The error code GD_E_OPEN_LINFILE has also been removed. It has been
+ split into two parts:
+ - I/O errors resulting from reading the LINTERP table file are now
+ reported using GD_E_IO;
+ - Syntax errors in the table are reported using the new GD_E_LUT error
+ code. GD_E_OPEN_LINFILE remains as a deprecated alias for GD_E_LUT.
- * gd_encoding_support() has been added to permit run-time determination of
- supported encodings.
+ * gd_encoding_support() has been added to permit run-time determination
+ of supported encodings.
- * gd_array_len() is the new name for gd_carray_len(). It now also handles
- STRING and SARRAY field types. The gd_carray_len() name remains in the
- library, but has been marked deprecated.
+ * gd_array_len() is the new name for gd_carray_len(). It now also
+ handles STRING and SARRAY field types. The gd_carray_len() name
+ remains in the library, but has been marked deprecated.
* BUG FIX: If the dirfile path provided cannot be resolved (due to, for
- instance, a symbolic link pointing to a non-existent path), gd_open() and
- friends now return GD_E_OPEN, as documented, instead of GD_E_RAW_IO.
+ instance, a symbolic link pointing to a non-existent path), gd_open()
+ and friends now return GD_E_OPEN, as documented, instead of
+ GD_E_RAW_IO.
* BUG FIX: gd_naliases() now returns an unsigned int, and zero on error,
as documented.
@@ -166,124 +174,132 @@
* PHP bindings have been added.
- * F77 and F95: The bindings no longer raise SIGABRT when the dirfile space is
- exhausted. Instead they simply return an invalid dirfile unit number.
+ * F77 and F95: The bindings no longer raise SIGABRT when the dirfile
+ space is exhausted. Instead they simply return a invalid dirfile unit
+ number.
- * F77: Functions to add fields with named scalar parameters have been added
- (GDASBT GDASCL GDASCP GDASCR GDASLC GDASMX GDASPH GDASPN GDASRC GDASRW
- GDASSB GDASWD), but only for those field types which permit named scalars.
- Similarly, functions for altering field metatdata with named scalars are
- also present (GDLSBT GDLSCL GDLSCP GDLSCR GDLSLC GDLSMX GDLSPH GDLSPN GDLSRC
- GDLSRW GDLSSB GDLSWD). These are provided as an alternative to using GDASCA
- after the fact.
+ * F77: Functions to add fields with named scalar parameters have been
+ added (GDASBT GDASCL GDASCP GDASCR GDASLC GDASMX GDASPH GDASPN GDASRC
+ GDASRW GDASSB GDASWD), but only for those field types which permit
+ named scalars. Similarly, functions for altering field metatdata with
+ named scalars are also present (GDLSBT GDLSCL GDLSCP GDLSCR GDLSLC
+ GDLSMX GDLSPH GDLSPN GDLSRC GDLSRW GDLSSB GDLSWD). These are provided
+ as an alternative to using GDASCA after the fact.
- * IDL: The entry structure parser has been rewritten. It no longer requires
- members which it doesn't need, and is also a lot more lax about numerical
- data types. Notably, it now ignores a supplied COMP_SCAL member. Floating
- point parameters can be specified in either the base name (M, B, A,
- DIVIDEND) or else the member prefixed with 'C' (CM, CB, CA, CDIVIDEND),
- whatever numerical type. The bindings will ingest them appropriately.
- Also, N_FIELDS and POLY_ORD, may be omitted, and will be calculated from the
- supplied data. A scalar IN_FIELDS is treated like an single element array.
+ * IDL: The entry structure parser has been rewritten. It no longer
+ requires members which it doesn't need, and is also a lot more lax
+ about numerical data types. Notably, it now ignores a supplied
+ COMP_SCAL member. Floating point parameters can be specified in either
+ the base name (M, B, A, DIVIDEND) or else the member prefixed with 'C'
+ (CM, CB, CA, CDIVIDEND), whatever numerical type. The bindings will
+ ingest them appropriately. Also, N_FIELDS and POLY_ORD, may be
+ omitted, and will be calculated from the supplied data. A scalar
+ IN_FIELDS is treated like an single element array.
- * PERL: The entry hash parser has been rewritten. It no longer requires keys
- which it doesn't need.
+ * PERL: The entry hash parser has been rewritten. It no longer requires
+ keys which it doesn't need.
- * PERL: alter_entry() now only updates defined elements in the passed entry
- hash.
+ * PERL: alter_entry() now only updates defined elements in the passed
+ entry hash.
* PYTHON: for backwards compatiblity, exceptions now exist for deprecated
- error codes (such as OpenError). These deprecated exceptions are simply
- aliases for the current ones and are never returned by the bindings.
+ error codes (such as OpenError). These deprecated exceptions are
+ simply aliases for the current ones and are never returned by the
+ bindings.
* F95 BUG FIX: fgd_add and fgd_alter_entry no longer ignore named scalar
parameters provided in supplied entry structures.
Miscellaneous:
- * The minimum autotools versions have been bumped. Autoconf-2.65 or newer,
- automake-1.13 or newer, and libtool-2.2.7b or newer are now required to
- rebuild the configure script and associated build environment. NOTE: In
- general, most people building GetData from a source release don't need the
- tools to build GetData; the autotools are only needed if changes need to be
- made to the configure script or Makefile input files provided in the
- release or if building from the repository.
+ * The minimum autotools versions have been bumped. Autoconf-2.65 or
+ newer, automake-1.13 or newer, and libtool-2.2.7b or newer are now
+ required to rebuild the configure script and associated build environ-
+ ment. NOTE: In general, most people building GetData from a source
+ release don't need the tools to build GetData; the autotools are only
+ needed if changes need to be made to the configure script or Makefile
+ input files provided in the release or if building from the repository.
-|==============================================================================|
+|=========================================================================|
New in version 0.8.6:
Library Changes:
* BUG FIX: Computation of LINCOMs with complex valued input fields now
- correctly happens in the complex plane. As a side effect, gd_native_type()
- now also correctly reports such LINCOM fields to be complex valued.
+ correctly happens in the complex plane. As a side effect,
+ gd_native_type() now also correctly reports such LINCOM fields to be
+ complex valued.
- * BUG FIX: The gd_[m]add() functions now ignore zero-length scalar strings.
- Previously they would store these invalid field codes, causing problems
- later.
+ * BUG FIX: The gd_[m]add() functions now ignore zero-length scalar
+ strings. Previously they would store these invalid field codes,
+ causing problems later.
* BUG FIX: Returning complex-valued CARRAYs as purely real now works.
- Previously only the first element requested would be returned, the remaining
- output buffer containing uninitialised data.
+ Previously only the first element requested would be returned, the
+ remaining output buffer containing uninitialised data.
- * BUG FIX: Entry members spf, bitnum, numbits, and period are now completely
- ignored by gd_[m]add() when corresponding named scalars are specified.
- Previously, an invalid value in these members would result in the entry
- being rejected, even though the rest of GetData ignored the invalid, unsued
- value.
+ * BUG FIX: Entry members spf, bitnum, numbits, and period are now com-
+ pletely ignored by gd_[m]add() when corresponding named scalars are
+ specified. Previously, an invalid value in these members would result
+ in the entry being rejected, even though the rest of GetData ignored
+ the invalid, unsued value.
* BUG FIX: The parsing of the \x and \u escape sequences is now correct.
* BUG FIX: A scalar field code specified for the last factor in a POLYNOM
entry is no longer ignored by gd_[m]add().
- * BUG FIX: gd_[m]add() no longer rejects MPLEX fields with negative count_val.
+ * BUG FIX: gd_[m]add() no longer rejects MPLEX fields with negative
+ count_val.
* BUG FIX: DIVIDE fields with complex-valued divisors are now properly
computed.
- * BUG FIX: Complex-valued POLYNOM and RECIP fields are now computed properly
- when the library is built in ANSI C mode.
+ * BUG FIX: Complex-valued POLYNOM and RECIP fields are now computed
+ properly when the library is built in ANSI C mode.
* BUG FIX: gd_alter_entry() no longer corrupts the DIRFILE when modifying
named scalars of MPLEX fields.
- * BUG FIX: Writing complex-valued MPLEX fields no longer corrupts the stored
- data.
+ * BUG FIX: Writing complex-valued MPLEX fields no longer corrupts the
+ stored data.
- * BUG FIX: gd_bof() now returns the correct number (i.e.: zero) when reporting
- the beginning of field of derived fields shifted to before the start of the
- dirfile. Previously, this function incorrectly returned values ranging from
- zero to one less than the samples-per-frame of the requested field.
+ * BUG FIX: gd_bof() now returns the correct number (i.e.: zero) when
+ reporting the beginning of field of derived fields shifted to before
+ the start of the dirfile. Previously, this function incorrectly
+ returned values ranging from zero to one less than the samples-per-
+ frame of the requested field.
* BUG FIX: gd_flush(), gd_sync(), gd_raw_close() no longer segfault when
operating on a LINCOM with only one input field.
* BUG FIX: gd_seek() now works correctly on PHASE fields; previously, the
sign of the PHASE shift was flipped.
- * BUG FIX: gd_seek() now correctly positions the virtual I/O pointer of the
- INDEX field.
+ * BUG FIX: gd_seek() now correctly positions the virtual I/O pointer of
+ the INDEX field.
- * BUG FIX: gd_framenum_subset() now returns the correct value when passed a
- field_end which is beyond the end of field, and then is required to
+ * BUG FIX: gd_framenum_subset() now returns the correct value when passed
+ a field_end which is beyond the end of field, and then is required to
extrapolate outside of the specified frame range.
- * BUG FIX: gd_error_string() now produces the correct string when reporting
- an out-of-range poly_ord encountered by gd_add_polynom() and similar.
+ * BUG FIX: gd_error_string() now produces the correct string when
+ reporting an out-of-range poly_ord encountered by gd_add_polynom() and
+ similar.
- * BUG FIX: gd_[m]alter_spec() no longer ignore co-efficients specified for
- POLYNOM entries.
+ * BUG FIX: gd_[m]alter_spec() no longer ignore co-efficients specified
+ for POLYNOM entries.
- * BUG FIX: gd_alter_encoding() now deletes the internal cache of RAW filenames
- of the affected fragment; previously, these old, cached filenames could lead
- to I/O errors when reading and writing the re-encoded RAW data files.
+ * BUG FIX: gd_alter_encoding() now deletes the internal cache of RAW
+ filenames of the affected fragment; previously, these old, cached
+ filenames could lead to I/O errors when reading and writing the re-
+ encoded RAW data files.
- * BUG FIX: Calling the Legacy API function GetFormat() on a Dirfile with MPLEX
- or WINDOW fields no longer results in a segmentation fault.
+ * BUG FIX: Calling the Legacy API function GetFormat() on a Dirfile with
+ MPLEX or WINDOW fields no longer results in a segmentation fault.
- * BUG FIX: Attempts to read past the EOF of a gzipped field no longer results
- in an I/O error, but successfully returns no data.
+ * BUG FIX: Attempts to read past the EOF of a gzipped field no longer
+ results in an I/O error, but successfully returns no data.
* BUG FIX: The internal recursion counter wasn't being properly reset on
certain error conditions, leading to spurious GD_E_RECURSE_LEVEL errors
@@ -291,8 +307,9 @@
Bindings Changes:
- * F77 and F95 BUG FIX: Named scalar indices are now indexed from one instead
- of zero, like all other array indices are in the Fortran GetData bindings.
+ * F77 and F95 BUG FIX: Named scalar indices are now indexed from one
+ instead of zero, like all other array indices are in the Fortran
+ GetData bindings.
* C++ BUG FIX: Fixed segfault in RawEntry destructor. Reported by S. J.
Benton.
@@ -301,217 +318,226 @@
entries when appropriate, instead of always returning zero. (The
RecipEntry::ComplexScalars() method always returned the correct value.)
- * IDL BUG FIX: The /UPDATEDB flag to gd_rename is no longer ignored; also, the
- /MOVE_DATA flag no longer also acts as if /UPDATEDB had been specified.
+ * IDL BUG FIX: The /UPDATEDB flag to gd_rename is no longer ignored;
+ also, the /MOVE_DATA flag no longer also acts as if /UPDATEDB had been
+ specified.
* PYTHON BUG FIX: The keyword for the "dirfile" parameter in the
getdata.fragment constructor is now properly spelled.
-|==============================================================================|
+|=========================================================================|
New in verison 0.8.5:
Library Changes:
- * BUG FIX: The zzslim encoding framework, which was inadvertantly rendered
- non-compilable in 0.8.4, should once again work. Reported by Matthew
- Hasselfield.
+ * BUG FIX: The zzslim encoding framework, which was inadvertantly
+ rendered non-compilable in 0.8.4, should once again work. Reported by
+ Matthew Hasselfield.
Bindings Changes:
* PYTHON BUG FIX: A spurious debugging message accidentally left in the
0.8.4 release has been expunged.
-|==============================================================================|
+|=========================================================================|
New in version 0.8.4:
Dirfile Changes:
* CLARIFICATION: Inconsistant behaviour in the library, coupled with
- contradictory statements in the Dirfile Standards, has resulted in confusion
- over the meaning of the final, optional, parameter in a MPLEX definition.
- To be clear: this parameter is simply the expected period between successive
- occurances of the "count" value in the index vector. (It is used by GetData
- only to figure out a resonable length for the MPLEX lookback.) The
- following clarifications and corrections have been made to the definition
- of the MPLEX field type in dirfile-format(5):
+ contradictory statements in the Dirfile Standards, has resulted in
+ confusion over the meaning of the final, optional, parameter in a MPLEX
+ definition. To be clear: this parameter is simply the expected period
+ between successive occurances of the "count" value in the index vector.
+ (It is used by GetData only to figure out a resonable length for the
+ MPLEX lookback.) The following clarifications and corrections have
+ been made to the definition of the MPLEX field type in
+ dirfile-format(5):
- - The final, optional parameter has been renamed from "max" to "period".
+ - The final, optional parameter has been renamed from "max" to
+ "period".
- - This parameter indicates not the maximal range of the index vector, as
- previously stated, but the expected number of samples between succes...
[truncated message content] |
Thanks for helping keep SourceForge clean.
X