Xref: utzoo comp.sys.amiga.tech:3625 comp.sys.amiga:28869 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!bbn!oberon!pollux.usc.edu!papa From: papa@pollux.usc.edu (Marco Papa) Newsgroups: comp.sys.amiga.tech,comp.sys.amiga Subject: Re: Multiple serial article from the European Developer's Conference Message-ID: <15185@oberon.USC.EDU> Date: 6 Feb 89 04:42:27 GMT References: <5877@cbmvax.UUCP> <3382@sugar.uu.net> <15154@oberon.USC.EDU> <3385@sugar.uu.net> Sender: news@oberon.USC.EDU Reply-To: papa@pollux.usc.edu (Marco Papa) Organization: Felsina Software, Los Angeles, CA Lines: 23 ||||ITn article limonce@pilot.njin.net (Tom Limoncelli) writes: >In ar.[^"-)U5{{ |[ this new serial-device stuff is a kludge ] | |In article <15154@oberon.USC.EDU|, papa@pollux.usc.edu (Marco Papa) doesn't |see the problem with it... |From my reading of the spec, it seems more like venders have two |options, first of all, they can supply their own serial.device (with a |different name of course) and have software get configured to look for |that device and a particular device number. Fine. If you don't like |the standard you can do it the "old" way and be perfectly conforming. Yep, if the "application" software is written in such a way as to allow USER selection of both DEVICE and UNIT, than one can have an application program work with BOTH a "conformant" serial.device or a "proprietary" whatever.device. -- Marco Papa 'Doc' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= uucp:...!pollux!papa BIX:papa ARPAnet:pollux!papa@oberon.usc.edu "There's Alpha, Beta, Gamma and Diga!" -- Leo Schwab [quoting Rick Unland] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=