26 Nov
2001
26 Nov
'01
11:10 a.m.
--- Sellam Ismail <foo(a)siconic.com> wrote:
On Mon, 26 Nov 2001, Ethan Dicks wrote:
Well... I _hadn't_ yet. I was still rolling around design ideas in my
head. I haven't written a byte of code yet. I really hadn't thought
that serial access was going to be a problem, but, I haven't ever tried
it from Perl. :-( I was contemplating passing a serial device descriptor
('/dev/ttyS01', '/dev/ttya', etc.) as part of the object constructor or
as a seperate method (i.e., $hcr->setSerialPort($port_name)). I must
admit that I never gave DOS/Win32 Perl a single thought. I was only
thinking of Solaris/Linux since that's what I run at home. I even have
Perl on my W2K laptop (from work) - I just don't ever have cause to run
it.
I was contemplating writing a Perl module to
front-end it (and hide
the AT syntax for setting/reading it)...
What Perl module are you using for serial port access? Or did you just
do a low level open of the serial device? I'm using Device::Serial,
which was modeled after the Win32 serial port routines and it sucks for
the most part. If you rolled your own, I would mind seeing the code.
I take it you meant "wouldn't"...
Serial ports under Unix are a bitch. I wanted to
create an alternate
Device::Serial module that would be much cleaner than the existing one.
I'll take your word for it. I wasn't expecting trouble in this area.
It wouldn't be as clean, but perhaps the main loop could open the serial
port in its own idiom and pass that open port descriptor to the
Chronograph object. Little messy, but it's _your_ problem to open the
port, not the Chronograph's problem.
As for where to put it on CPAN, I would suggest:
Operating_System_Interfaces/Hardware
I'll look into that area and see what else is hanging around. Thanks for
the suggestion.
-ethan
__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1