Message-ID: <444B92DE.6010107@vecernik.at>
Date: Sun, 23 Apr 2006 16:44:46 +0200
From: Oliver Vecernik <spam@vecernik.at>
Reply-To: ov@vecernik.at
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8) Gecko/20051201 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: serial ports
References: <036501c666c4$4a397320$a501a8c0@CAM.ARTIMI.COM>
In-Reply-To: <036501c666c4$4a397320$a501a8c0@CAM.ARTIMI.COM>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Dave Korn schrieb:
>   Trying to mix win32 perl and cygwin is a recipe for tears.  Sure, use CPAN
> modules, that is of course a good idea; but if the *nix one doesn't work under
> cygwin, fixing it or rolling your own or even just using the bog-standard file
> i/o features in perl is definitely far safer.

  First of all: I was just missing the fact, that /dev/ttyS3 is there
but did not show up in `ls /dev/ttyS3' as Igor stated.  Thanks for the hint.

  I'm still no perl expert and I have to learn "the correct way to do
it".  I want to write my modules as portable as possible and Cygwin
seems to be the best approach.  :-)

  I'm trying to get rid of using Visual Basic on Windows, which I used a
lot in the past for such kind of things including using com ports.  I
installed Device::SerialPort altough some tests fail.  I'm trying to
find out why, but this may take some time and is probably not related
with Cygwin anymore.

-- 
Cheers,
Oliver

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/