Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: Standard or Forth? Date: Thu, 08 Sep 2016 21:50:27 -0700 Organization: A noiseless patient Spider Lines: 17 Message-ID: <877falllrg.fsf@jester.gateway.pace.com> References: <57cb5023.1577548706@news.eternal-september.org> <87shtakwlt.fsf@jester.gateway.pace.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="590ea01354cf4bcbcd857d7ebbd88128"; logging-data="21768"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18I2d2vAXbkx/Z2t5Cm0tFw" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:WAytSUflDluyO+AHqPQ8zKQn6os= sha1:10+qsrs+PF8Erxc/RsgPW9ipu5s= Xref: csiph.com comp.lang.forth:50767 "HAA" writes: > When the realization occurs that ANS hasn't, and 200x won't, deliver > the promised world of portable programs, then a forther is free. What promised world of portable programs? I've never seen a portable C program (one with no system-dependent #ifdef's) of any size. Even Java ("write once, debug everywhere") is less portable than some like to think. > Free to take the best from standards and ignore the rest. If the standard describes a workable way to do something and there's not a substantial concrete benefit from doing something different, I don't see good reason to depart from it. The standard envisages a fairly traditional approach to implementation though. If you want to use a very different approach (like Oforth in one direction, or Colorforth in another) then ignoring the standard except as a distant source of inspiration is more likely the way to go.