Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!ames!mailrus!iuvax!purdue!umd5!brl-adm!brl-smoke!gwyn From: gwyn@brl-smoke.ARPA (Doug Gwyn ) Newsgroups: comp.lang.c Subject: Re: Self-modifying code Message-ID: <8239@brl-smoke.ARPA> Date: 11 Jul 88 13:59:03 GMT References: <12330@ut-sally.UUCP> <225800044@uxe.cso.uiuc.edu> Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB)) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 16 In article <225800044@uxe.cso.uiuc.edu> mcdonald@uxe.cso.uiuc.edu writes: >I can do three things: Although you didn't spell out the details of your situation, I'm sure there are quite a few other possibilities. For example, one can index an array to obtain the switch flag. As a significant example of C's efficiency for graphics programming, virtually all the code in the Blit, DMD (5620), and MTG (630) bitmapped terminals was written in C, and their graphics operations are extremely fast. No self-modifying code was necessary. One of my "back burner" projects is to produce a display-list driven interactive 3D viewer for these terminals (and probably port it to Suns). I have no doubt that it can be done quite nicely while sticking to the C language rules.