Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: Question about checking the stack Date: Sat, 28 Nov 2015 19:17:32 -0800 Organization: A noiseless patient Spider Lines: 9 Message-ID: <87poyteboz.fsf@jester.gateway.pace.com> References: <87io4qh7fm.fsf@nightsong.com> <87k2p5g4n0.fsf@nightsong.com> <8737vtfrk9.fsf@nightsong.com> <47ydnYNjvc2dHcvLnZ2dnUU7-Yv46u6z@supernews.com> <87y4dldyuu.fsf@nightsong.com> <39c6cda5-fd60-4d19-85a3-c732e102a02b@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="d09d25b6b873a1567c8bb21cd9fda25b"; logging-data="13445"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/CFZkoCsKG5fAvbA/7Dq5d" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:DGE8NVPdJV9zH+FPX721jceufrI= sha1:PBCjrrqeS9sC6qwy7jjkgJOclJQ= Xref: csiph.com comp.lang.forth:43925 "Elizabeth D. Rather" writes: > Yes, but those "few microseconds" become attached to virtually > everything you do, at which point they add up to a measurable > overhead. It seems to me that a serious compiler can track the stack picture and eliminate the checks most of the time. A naive interpreter might take a noticable slowdown from the checks, but if you're using such an interpreter, you're not too worried about speed anyway.