From ... Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!news-FFM2.ecrc.net!uio.no!nntp.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: (open :direction :probe ...) vs probe-file Date: 24 Jan 2004 14:44:30 +0000 Organization: Naggum Software, Oslo, Norway Lines: 29 Message-ID: <3283944270455837KL2065E@naggum.no> References: <3283929265717785KL2065E@naggum.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: readme.uio.no 1074955470 4155 129.240.65.201 (24 Jan 2004 14:44:30 GMT) X-Complaints-To: abuse@uio.no NNTP-Posting-Date: Sat, 24 Jan 2004 14:44:30 +0000 (UTC) Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 Xref: archiver1.google.com comp.lang.lisp:10672 * Peter Seibel | I admit I hadn't thought of using it to carry around the element-type | information for later use. Not only that, it is useful to remember the external-format argument to be used to open a particular file. The pathname is unable to carry all this information around. | I never realized that passing a stream as a pathname designator to | OPEN *should* convey anything more than the name of the file that the | stream was associated with. I just reread the OPEN dictionary entry | and didn't see anything to suggest that; did I miss it or is it | somewhere else in the spec? No, it just falls in the category of my reasonable expectations, which may or may not be codified or shared by others. Now I realize that I had written my own open that effectively did (open ... :element-type (stream-element-type ) :external-format (stream-external-format )) in addition to figuring out the direction of the stream if :direction was not explicitly specified. -- Erik Naggum | Oslo, Norway Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.