Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!willett!ForthNet
From: ForthNet@willett.UUCP (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: HS/Forth
Message-ID: <685.UUL1.3#5129@willett.UUCP>
Date: 21 Mar 90 00:14:23 GMT
Organization: Latest link in the ForthNet chain.  (Pgh, PA)
Lines: 35


 Date: 03-19-90 (16:13)              Number: 3046 (Echo)
   To: BILL MCCARTHY                 Refer#: 3043
 From: STEVE PALINCSAR                 Read: 03-19-90 (23:03)
 Subj: NEW RELEASE OF HS/FORTH       Status: PUBLIC MESSAGE

 Bill, I passed your comments and benchmark tests on to Jim Callahan at 
 HS/Forth.  He has the following comments:

 1.  Indeed, as you point out, FORTRAN must be loaded before RSTACK.  
 However, he thinks if you're going to be loading fortran you will not be
 loading rstack anyway.

 2.  The $+ bug you've mentioned has now been fixed.

 3.  Regarding the timings, there is indeed a speed penalty in using 
 FORTE.  However Jim says you have selected a worst case scenario to 
 test.  In any test that used logs, exponentials or trig functions, those
 would dominate the test and would strongly affect timing.  In addition, 
 he says FORTE is more for convenience in entering formulas than for 
 speed in processing.  If you seriously needed to crunch 25,000 times 
 you'd be much better off using optimized VARs -- as you have 
 demonstrated.  He also said you might very well be able to optimize the 
 FORTE code.

 He did go on to say that future releases would probably increase the 
 speed in the fortran package.

 It's interesting to note in your benchmarks (this is me now, not Jim) 
 the three-fold advantage HS has over F-PC without optimization.  Also 
 interesting to see how close the timing is for optimized HS vs turbo 
 pascal: those timings are so close as to be essentially identical.
-----
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'