Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!genrad!teddy!panda!talcott!harvard!seismo!brl-tgr!tgr!Lee.Sailer@CMU-CS-C.ARPA From: Lee.Sailer@CMU-CS-C.ARPA Newsgroups: net.micro.cpm Subject: Turbo Message-ID: <7272@brl-tgr.ARPA> Date: Sun, 13-Jan-85 12:48:30 EST Article-I.D.: brl-tgr.7272 Posted: Sun Jan 13 12:48:30 1985 Date-Received: Wed, 16-Jan-85 16:04:48 EST Sender: news@brl-tgr.ARPA Organization: Ballistic Research Lab Lines: 30 So far, except for Kahn's assurance that it is really simple, it seems that nobody is willing to admit that they know how it works. Here is a new, simpler question: 1. Is anybody out there trying to figure out how Turbo "does it"? 2. Is anybody debating what it could do better, so that version x will be even spiffier? Here are a few of my own (somehat trivial) wishes. - A stand-alone version of the editor/run-time system. TRUE FACT. I use Turbo as my editor when writing in C. ("Why?" is a lng story.) - A utility that will strip out totally unused parts of .COM files. if, for example, Turbo loads all the trig functions into every .COM file, could a utility dtect that they were never used, and squeeze them out? - Turbo's random number generator is not so hot. In paticular, it cannot be started from a particular seed. Patches? - Could Turbo be patched to add a "true" complex type, and thereby save us all from those letters in BYTE that say "Real men use FORTRAN!" Of Course! First, someone (not me, sorry, I don't even know assembler) will have to figure out how Turbo is possible, period. thanks for listening -------