Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!willett!ForthNet
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: FORTH FOR VAX 11/780
Message-ID: <2543.UUL1.3#5129@willett.pgh.pa.us>
Date: 29 Mar 91 23:30:29 GMT
Organization: (n.) to be organized.  But that's not important right now.
Lines: 33


 Date: 03-14-91 (08:21)              Number: 1503 of 1557
   To: ALL                           Refer#: NONE
 From: CHARLIE HITSELBERGER            Read: (N/A)
 Subj: VAX FORTH                     Status: PUBLIC MESSAGE
 Conf: FORTH (58)                 Read Type: GENERAL (+)

 To whomever asked about Forth on the VAX, I have both the fig-Forth
 which runs under VMS 4.xx, as well as VAX Forthsim/VMS.

 The fig forth is dodgy (uses blocks, but they're stored in files... only
 supports VT100... flips on the high bit when displaying a VLIST... not
 Forth-79 or Forth-83...) and shouldn't be used.

 Whereas, on the other hand, the VAX Forthsim/VMS V3.2 is awesome.  It's
 got RMS file support, store source in files, system service calls,
 debugging tools, compiles to native code, optimization, etc...   It
 requires VMS 5.2 or greater to run.  Alas, my terminal program does not
 support Xmodem or Ymodem file transfers, and I have never been able to
 make Kermit uploads function.  If you'll mail me your address and
 what-not, I'll stick the savesets on your choice of TK-50 or 8mm.
 Exabyte tape and send them off to you, free of charge.

 Charlie Hitselberger

 PCRelay:DCINFO -> #16 MetroLink (tm) International Network
 4.10              DC Info Exchange MetroLink International Hub
 <<<>>>
-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us _or_ uunet!willett!dwp