Newsgroups: alt.lang.design,comp.lang.c++,comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!hookup!europa.eng.gtefsd.com!howland.reston.ans.net!gatech!rutgers!att-out!nntpa!nntpa.cb.att.com!lgm
From: lgm@polaris.ih.att.com (Lawrence G. Mayka)
Subject: Re: Comparing productivity: LisP against C++ (was Re: Reference Counting)
In-Reply-To: lyman@cc.gatech.edu's message of 21 Dec 1994 14:16:52 -0500
Message-ID: <LGM.94Dec22080822@polaris.ih.att.com>
Sender: news@nntpa.cb.att.com (Netnews Administration)
Nntp-Posting-Host: polaris.ih.att.com
Organization: AT&T Bell Laboratories, Naperville, Illinois, USA
References: <19941203T221402Z.enag@naggum.no> <vogtD12y8D.HLL@netcom.com>
	<3d5alh$6j7@celebrian.otago.ac.nz> <3d8j9r$cm9@celebrian.otago.ac.nz>
	<3d9uv4$rkh@pravda.cc.gatech.edu>
Date: Thu, 22 Dec 1994 14:08:22 GMT
Lines: 22
Xref: glinda.oz.cs.cmu.edu comp.lang.c++:104515 comp.lang.lisp:16147

In article <3d9uv4$rkh@pravda.cc.gatech.edu> lyman@cc.gatech.edu (Lyman S. Taylor) writes:

   The MAJOR speed difference between these programers is that C's std library
   has routines that can read/write blocks of bytes at a 
   time and Lisp's std. library doesn't.  Big deal!  Any decent Lisp vendor 
   could add that into a lisp implementation in a small amount of time.  

   However, as was expressed ( several people saying... "I don't normally do
   file I/O in Lisp ... I had to look it up" ),  doing file I/O is not something
   most Lisp users preoccupy themselves with. Therefore, I don't expect very
   many vendors to run out and add this "feature".

Actually, the ANSI standard for Common Lisp includes READ-SEQUENCE and
WRITE-SEQUENCE, which are meant for this very purpose; but X3J13 added
these two functions rather recently, so vendors may not support them
portably yet.
--
        Lawrence G. Mayka
        AT&T Bell Laboratories
        lgm@ieain.att.com

Standard disclaimer.
