Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!willett!ForthNet
From: ForthNet@willett.UUCP (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: Non-Forth systems/languages.
Message-ID: <461.UUL1.3#5129@willett.UUCP>
Date: 13 Feb 90 23:36:39 GMT
Organization: Latest link in the ForthNet chain.  (Pgh, PA)
Lines: 28


 Date: 02-11-90 (19:14)              Number: 2899 (Echo)
   To: LEE BROTZMAN                  Refer#: NONE
 From: ZAFAR ESSAK                     Read: NO
 Subj: C  STREAMS                    Status: PUBLIC MESSAGE

 I have taken a portion from the discussion in the Modula-2 area in the 
 hope that it can be expanded on. 

 LB>  C is built on the "streams concept", making all input and output, 
 LB>  regardless of origin, look like a file. 
 LB>  That is both a blessing and a curse. 

 Could you please elaborate on how the Stream approach is a curse. 
 Having used Forth for many years without Streams I was surprised at the 
 ease with which a number of problems could be solved once stream I/O 
 was added to Forth.  This was especially true of data translation from 
 one format to another.  I am inclined to think that stream I/O should 
 be made a fundamental component of Forth, after all doesn't the 
 interpreter view input as a "stream" coming either from the keyboard or 
 mass storage? 
 ---
  * Via Qwikmail 2.01

 NET/Mail : British Columbia Forth Board - Burnaby BC - (604)434-5886   
-----
This message came from GEnie via willett through a semi-automated process.
Report problems to: 'uunet!willett!dwp' or 'willett!dwp@gateway.sei.cmu.edu'