X-Spam-Check-By: sourceware.org From: "David Christensen" To: Subject: RE: serial ports Date: Sat, 22 Apr 2006 21:44:13 -0700 Message-ID: <007901c66690$98f11ce0$0a01a8c0@p42800e> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <02dd01c66603$42bb6430$a501a8c0@CAM.ARTIMI.COM> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Dave Korn wrote: > Well then, that's a really good argument for just using the builtin > access that cygwin provides through /dev/ttySx instead, isn't it? > The way Oliver's original post reads suggests that he was just thrown > off by not seeing any devices under the virtual /dev dir, but that > doesn't mean it won't work for him if he tries it. As they say in Perl parlance, TIMTOWDI ("there's more than one way to do it"). If Oliver is a C, etc., programmer fluent in the /dev/ttySx API, then it could work. But if Oliver wants to write idiomatic Perl and get his application going faster and easier, then he wants to use standard and accepted CPAN libraries rather than roll his own (especially non-portable ones). Win32::SerialPort (Windows) and Device::SerialPort (Unix/Linux) are the best approach under Perl. One or both may work under Cygwin; I haven't done serial port programming in a number of years, and needed ActiveState Perl the last time I did. YMMV. David -- 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/