| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
0-result from method 'limit?' of transformations. Return the
number of copied bytes instead, which is possibly nothing. The
latter then triggers EOF handling in the higher layers, making the
0-result of limit? the way to inject artificial EOF's into the
data stream.
|
|
|
|
|
|
|
| |
* generic/tclIORTrans.c (ReflectClose): Closing a channel may
supply NULL for the 'interp'. Test for finalization needs to be
different, and one place has to pull the interp out of the channel
instead.
|
|
|
|
| |
etc.)
|
| |
|
|
|
|
| |
debug output in C++ comment.
|
|
|
|
|
| |
const tables. No functional
or API change.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Pat Thoyts <patthoyts@users.sourceforge.net>. Reset the EOF flag
after draining the Tcl level into the result buffer, to make sure
that the result buffer will be drained as well by repeated calls
to ReflectInput should it contain more than one buffer-full of
data. Without that reset the higher I/O system will not call on
ReflectInput anymore due to the assumed EOF, thus losing the data
which did not fit in the buffer of the call which caused the eof
and drain.
|
|
* generic/tclIOCmd.c: Integration of transform commands into 'chan' ensemble.
* generic/tclInt.h: Definitions of the transform commands.
* generic/tclIORTrans.c: Implementation of the reflection transforms.
* tests/chan.test: Tests updated for new sub-commands of 'chan'.
* tests/ioCmd.test: Tests updated for new sub-commands of 'chan'.
* tests/ioTrans.test: Whole new set of tests for the reflection transform.
* unix/Makefile.in: Integration of new files into build rules.
* win/Makefile.in: Integration of new files into build rules.
* win/makefile.vc: Integration of new files into build rules.
NOTE: The file 'tclIORTrans.c' has a lot of code in common with
the file 'tclIORChan.c', as that made it much easier to
develop the reference implementation as a separate
module. Now that the transforms have been committed the one
thing left to do is to go over both modules and see which of
the common parts we can factor out and share.
|