From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fac41,9a0ff0bffdf63657 X-Google-Attributes: gidfac41,public X-Google-Thread: f43e6,9a0ff0bffdf63657 X-Google-Attributes: gidf43e6,public X-Google-Thread: 103376,4b06f8f15f01a568 X-Google-Attributes: gid103376,public X-Google-Thread: 1108a1,9a0ff0bffdf63657 X-Google-Attributes: gid1108a1,public From: dennison@telepath.com Subject: Optimizations (was: Software landmines (loops)) Date: 1998/09/01 Message-ID: <6sh487$lnq$1@nnrp1.dejanews.com>#1/1 X-Deja-AN: 386790353 References: <902934874.2099.0.nnrp-10.c246a717@news.demon.co.uk> <6r1glm$bvh$1@nnrp1.dejanews.com> <6r9f8h$jtm$1@nnrp1.dejanews.com> <6renh8$ga7$1@nnrp1.dejanews.com> <6rf59b$2ud$1@nnrp1.dejanews.com> <6rfra4$rul$1@nnrp1.dejanews.com> <35DBDD24.D003404D@calfp.co.uk> <6sbuod$fra$1@hirame.wwa.com> <35f51e53.48044143@ <904556531.666222@miso.it.uq.edu.au> <35EAEC47.164424A7@s054.aone.net.au> <6sgn8l$7aq$1@nnrp1.dejanews.com> X-Http-Proxy: 1.0 x2.dejanews.com:80 (Squid/1.1.22) for client 204.48.27.130 Organization: Deja News - The Leader in Internet Discussion X-Article-Creation-Date: Tue Sep 01 15:35:35 1998 GMT Newsgroups: comp.lang.eiffel,comp.object,comp.software-eng,comp.lang.ada X-Http-User-Agent: Mozilla/4.05 [en] (WinNT; I) Date: 1998-09-01T00:00:00+00:00 List-Id: In article <6sgn8l$7aq$1@nnrp1.dejanews.com>, dewarr@my-dejanews.com wrote: > few compilers do this optimization. A similar case is optimizing > an awkward case statement of a finite state machine back to the > simple and efficient version with gotos. > > Given how common serious goto-allergy is, especially in the > US, and seeing how many people are willing to contort their > code to avoid gotos, these are optimizations that are probably > worthwhile including in modern compilers for this class of > languages. Being one of those goto-phobes as well a big fan of case statements, this subject interests me. I assumed the relatively strict rules on case statement predicates were specifically formulated so that they could be implemented as jump-tables. Is that not the case? Is there anything that I can do to my case statements to help the compiler out a bit? -- T.E.D. -----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum