Am Di., 21. Apr. 2020 um 09:40 Uhr schrieb Shiro Kawai <xxxxxx@gmail.com>:

[...]

>
> Then, if you already have C read / write for ordinary ports, it seems that you have to duplicate the functionality for the custom ports.  Isn't it?
> (Or, the custom port's read/write can does two-pass; e.g. it first writes to string port using C write, then emits the intermediate string to the sink.  Is it what you have in mind?)

I didn't mean to duplicate the functionality. The custom port `read'
and `write' methods should eventually call the C versions, so they
should be thin wrappers that intercept non-local control flow and do
the buffering. As these methods are implementation-wise port-specific,
they can make use of whatever functionality the port implementation
offers to buffer.