transform query/maxRead bug ?
Brought to you by:
andreas_kupries,
patthoyts
I am using the transform -attach mode in trf
in conjunction with the query/maxRead function
to read in fixed length data blocks, and I have
noticed that the code ignores a second max read value
if it is smaller than the first time it is set.
In my code I am setting max read to 4 bytes, and then
reading the 4 bytes. In the initial 4 bytes I store the
information
(size) for the next max read value. The TrfInput subroutine
does not use the next max read value if it is smaller
than the first.
The documentation leads the user to believe that they
can redefine
the max read value, and the code will actually use that
value. Why does the author query the max read value on
every block read if
additional values are ignored.
Thank you.
Jeff Gilbertson