On Mon, May 23, 2011 at 08:05:18PM +0100, Paul LeoNerd Evans wrote:
> I've been getting annoyed lately at the awkward and insane steps
> required to go through just to get a serial device
On Wed, May 25, 2011 at 11:21:50PM +0200, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 wrote:
> > I've missed something totally nonobvious
> I've missed something totally nonobvious on
> CPAN
Device::SerialPort? If you know it, then write a piece of contrasting
documentation so that a potential user can make an informed decision to employ
your module over D::S or vice-versa.
If that's too abstract, put yourself in my shoes when wri
On Tue, May 24, 2011 at 12:57:20PM -0700, Austin Schutz wrote:
>
> IO::Tty. IO::Stty.
IO::Tty is useful and contains constants and so on, but it isn't an
IO::Handle subclass. Can be quite cute.
IO::Stty is also not an IO::Handle subclass, and has a somewhat odd
interface.
> I don't see what thi
IO::Tty. IO::Stty.
I don't see what this really adds above and beyond the core POSIX module
and those two, but if you really like your "combined" syntax I guess
that's something.
Austin
Paul LeoNerd Evans wrote:
I've been getting annoyed lately at the awkward and insane steps
required to
I've been getting annoyed lately at the awkward and insane steps
required to go through just to get a serial device, or hack around at
the termios flags of STDIN/etc... To this end, I've written the
following module, called IO::Termios.
Some future plans involve:
* Adding more getflag_*/setflag_
