Newsgroups: comp.lang.dylan
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!news.dfci.harvard.edu!camelot.ccs.neu.edu!chaos.dac.neu.edu!usenet.eel.ufl.edu!news.mathworks.com!tank.news.pipex.net!pipex!howland.reston.ans.net!news.sprintlink.net!malgudi.oar.net!chemabs!lwv26
From: lwv26@cas.org (Larry W. Virden)
Subject: Re: Portable File Handling for Dylan
Content-Type: text/plain; charset=US-ASCII
Message-ID: <1995Sep11.181241.8536@chemabs.uucp>
Sender: lwv26@chemabs.uucp (Larry W. Virden)
Reply-To: lvirden@cas.org
Content-Transfer-Encoding: 7BIT
Organization: Nedriv Software and Shoe Shiners, Uninc.
References: <1995Sep5.085417@engr.sgi.com> <23210.9509081359@bakura.harlequin.com>
Mime-Version: 1.0
Date: Mon, 11 Sep 1995 18:12:41 GMT
Lines: 20


In article <23210.9509081359@bakura.harlequin.com>,
Scott McKay <swm@harlequin.com> wrote:
:     This is precisely the problem that I was afraid was going to happen once Apple
:   releases their commercial version, only Harlequin beat them to it. Once Apple

:Since we're talking about layered libraries here, I don't see any
:problem with porting the Harlqn streams library to Apple.  There are

Oh, was Harly, Apple, etc. going to be releasing source code?  That seems
like it would change the matter.  In the past, the problem that many of
us saw, which I thought Scott McKay was referencing, was that having libraries
without source, and having folk threaten lawsuits over reverse-engineering,etc.
made it unlikely that compatible libraries would evolve across platforms.

-- 
:s Larry W. Virden                 INET: larry.virden@cas.org
:s A good scientist always hedges his bets.  Ramos
:s Unless explicitly stated to the contrary, nothing in this posting should 
:s be construed as representing my employer's opinions.
