Re: Re: [Sisc-users] (non-)Binary ports and warnings

"Alessandro Colomba" <[email protected]> writes:

> On 3/14/06, Matthias Radestock <[email protected]> wrote:
> [...]
>>
>> We probably also want methods to create serial ports (c.f. the
>> serial-io module) from Java streams.
> [...]
>> > One could opt to leave 3 and 5 out, and have users adopt the
>> > open-character-*-port methods from the generic-io module (since they
>> > "upgrade" a port to a chracter port).
>>
>> I think I'd prefer that.
>
> It seems to me that these two options are connected. Both
> open-serial-*-port and open-character-*-port turn a "binary" port to
> the desired type, making a direct conversion from a Java *Stream
> redundant, if convenient.
>
> Wouldn't we want to either leave both conversions in or out together?

Good point. I was looking at the code and noticed that
open-serial-*-port is implemented quite differently to
open-character-*-port - the former calls a primitive whereas the latter
uses s2j. However, you are right that they actually work in much the
same way.

In that case all four functions should be left out from your java-io
module.


Matthias.



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642