LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (February 1996)Back to main REXXLIST pageJoin or leave REXXLIST (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Wed, 14 Feb 1996 07:26:03 GMT
Reply-To:     REXX Programming discussion list <REXXLIST@UGA.CC.UGA.EDU>
Sender:       REXX Programming discussion list <REXXLIST@UGA.CC.UGA.EDU>
From:         Warren Hall <warren@BORG.COM>
Organization: Team OS/2
Subject:      Re: What REXX commands are CPU hogs ?

In <ipsperDMHu74.EAM@netcom.com>, ipsper@netcom.com (Intergrated Perf Svcs #5730) writes: >I attended a very entertaining session by Rick McGuire at the last SHARE. >It was titled "REXX Performance". Rick asked the audience for things they >had heard about REXX performance, then proceeded to debunk almost everything. >Most things vary from platform to platform, between compiler and interpreter, >and change with PTFs or versions. Some were just plain false! >Good algorithms will stand the test of time. >If you care enough about performance to look at individual instructions, >you probably need to use another language. REXX is mostly interpreted, >and even compiled REXX isn't very efficient. > >Alan Ackerman, usboatbb@ibmmail.com >-- >Bank of America >Integrated Performance Services #5730

Like a driver: attend to your destination, the brakes, accellerator, rear-view mirror, and traffic. The octane rating will attend to itself. In any event, the mileage will vary! But safe driving will tell.

Warren http://www.borg.com/~warren


Back to: Top of message | Previous page | Main REXXLIST page