Newsgroups: comp.lang.dylan
Path: cantaloupe.srv.cs.cmu.edu!rochester!udel!gatech!swrinde!tank.news.pipex.net!pipex!uknet!newsfeed.ed.ac.uk!edcogsci!jeff
From: jeff@cogsci.ed.ac.uk (Jeff Dalton)
Subject: Re: part 2 of re: File handling in Dylan
Message-ID: <DE30qM.C2v@cogsci.ed.ac.uk>
Organization: Centre for Cognitive Science, Edinburgh, UK
References: <27858.9508281705@subnode.aiai.ed.ac.uk> <41tq2u$8r5@cantaloupe.srv.cs.cmu.edu>
Date: Tue, 29 Aug 1995 17:03:55 GMT
Lines: 31

sef@CS.CMU.EDU (Scott Fahlman) writes:

>In article <27858.9508281705@subnode.aiai.ed.ac.uk> jeff@aiai.ed.ac.uk (Jeff Dalton) writes:

>> > We decided to delegate file handling to native API's.
>> 
>> There have been a couple of issues now for which developers seem
>> to be the obstacle to agreement on a common way of doing things.
>> 
>> I've often thought, when looking at other standardizations (which
>> I mean in an informal and general sense, not just official ANSI,
>> ISO, etc standardizations), that it was fortunate that the language
>> got as far as it did before this kind of disagreement blocked
>> further progress.

>Well, don't give up on Dylan just yet.  At least, not for this
>reason. :-)

>I think that all the major implementation groups understand that with
>so many essential features pushed out of the core language and into
>libraries, agreement on a set of standard libraries that will make up
>"greater Dylan" is absolutely essential.  Some implementations may
>omit certain libraries that don't make sense in their environment, or
>may deviate from the standard for some good reason, but we do plan to
>proceed in the spirit of "If you're going to do this, do it this way"

Excellent!

Glad to hear it.

-- jeff
