in reply to Difference Between Device::SerialPort and Win32::SerialPort
Does anyone know of a way around this?From what I've read, anyone who RTFMs (see timeouts in the manual).
I prefer the Device::SerialPort semantics.According to the docs, Device::SerialPort doesn't have semantics and Any discrepancies or omissions should be considered bugs and reported to the maintainer. The read differences are documented, so I guess they're not "bugs" anymore.
Can Device::SerialPort be used successfully under Windows?Have you tried it? Did you look at the source? Did you check cpan-testers? Having done all 3 my guess would be no, esp. since there is no point (since Device::SerialPort is supposed to be Win32::SerialPort for unices).
Are there other differences between the two modules?Yes. They're documented in Device::SerialPort. Here's a little quote The read method, and tied methods which call it, currently can use a fixed timeout which approximates behavior of the Win32::SerialPort...
PS - I haven't actually used either of these modules to develop apps, but I sure can RTFM :)
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: Difference Between Device::SerialPort and Win32::SerialPort
by Belgarion (Chaplain) on Apr 16, 2004 at 03:18 UTC |