[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: binary vs non-binary ports

To: srfi-56@xxxxxxxxxxxxxxxxx
Subject: Re: binary vs non-binary ports
From: Alex Shinn <foof@xxxxxxxxxxxxx>
Date: Fri, 17 Sep 2004 00:32:23 -0500
Delivered-to: srfi-56@xxxxxxxxxxxxxxxxx
In-reply-to: <86isady2z5.wl@xxxxxxxxxxxxxxxx>
References: <41491BE0.50006@xxxxxxxxxxx> <20040915.223004.159263589.shiro@xxxxxxxx> <86isady2z5.wl@xxxxxxxxxxxxxxxx>
User-agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.3 (i386-pc-linux-gnu) MULE/5.0 (SAKAKI)

At Thu, 16 Sep 2004 22:43:42 -0500, Alex Shinn wrote:
> 
> A possible way to get more portability is to go ahead and provide the
> API for specifying port types, such as
> 
>   (open-input-port <path>)     ; character port
>   (open-input-port <path> #t)  ; binary port

That was supposed to be open-input-file.

-- 
Alex

Follow-Ups:
- Re: binary vs non-binary ports
  - From: Per Bothner

References:
- binary vs non-binary ports
  - From: Per Bothner
- Re: binary vs non-binary ports
  - From: Shiro Kawai
- Re: binary vs non-binary ports
  - From: Alex Shinn

Prev by Date: Re: binary vs non-binary ports
Next by Date: opening and closing binary files
Previous by thread: Re: binary vs non-binary ports
Next by thread: Re: binary vs non-binary ports
Index(es):
- Date
- Thread