Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.forth > #58427

Re: microFORTH

From "HAA" <someone@microsoft.com>
Newsgroups comp.lang.forth
Subject Re: microFORTH
Date 2017-05-01 11:15 +1000
Organization Aioe.org NNTP Server
Message-ID <oe62bf$qns$1@gioia.aioe.org> (permalink)
References <2d438ef9-36ec-42b6-b98f-792dcc3798db@googlegroups.com><odomhc$1fp3$1@gioia.aioe.org> <8PidneLnT8Uxe2LFnZ2dnUU7-V3NnZ2d@supernews.com>

Show all headers | View raw


Elizabeth D. Rather wrote:
> On 4/25/17 1:35 PM, HAA wrote:
> > JUERGEN wrote:
> >> microFORTH documentation is available on the FORTH, INC. website. Not a new product -
> >> but many here will probably remember it. And might have a look after many years ...
> >>
> >> +++++++++++++++++++++++++++++++++++++++++++++++++
> >> Forth has been around a long time. It would be a mistake to look at any of these
> >> early systems and think they represent today's standards-based, commercial-grade
> >> Forth products. However, there is much to learn from the work of others and Forth's
> >> history is studded with some stunning examples of both systems and applications.
> >> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>
> >>
> >> https://www.forth.com/resources/archive-forth-systems-software/
> >
> > Thanks for that.
> >
> > I never knew Fig-Forth was *that* close to microFORTH.  I had assumed
> > 0 VARIABLE <BUILDS  END  etc were a Fig-Forth invention.
>
> According to Don Colburn, writing in the History of Programming Languages
> paper http://www.forth.com/resources/forth-programming-language/ the first
> figForth was written by Maj. Robert Selzer, who had used microFORTH for an
> AMI 6800 development system on an Army project and was privately developing
> a standalone editor/assembler/linker package for the 6502. Selzer wrote a
> 6502 Forth assembler, and used the Army’s microFORTH metacompiler to target
> compile the first 6502 stand-alone Forth for the Jolt single board computer.
> He completed the project with Bill Ragsdale, who used it in his business
> and then published it for FIG.
>
> Cheers,
> Elizabeth

A closer look at microFORTH reveals it was also quite different from Forth
we know today.  There was no AGAIN or REPEAT.  UNTIL was called END.
Backslash '\' was COMPILE.  WHILE worked like REPEAT but resolved a
preceding IF/ELSE.  FILL had no resemblance to today's word.

In comparison Fig-Forth, which came out not long after, looks relatively
modern.  So while Fig-Forth's origin may have been microFORTH, its
influences appear to have extended well beyond.


Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

microFORTH JUERGEN <epldfpga@aol.com> - 2017-04-25 01:15 -0700
  Re: microFORTH "HAA" <someone@microsoft.com> - 2017-04-26 09:35 +1000
    Re: microFORTH "Elizabeth D. Rather" <erather@forth.com> - 2017-04-25 14:15 -1000
      Re: microFORTH lehs <skydda.barnen@gmail.com> - 2017-04-25 23:09 -0700
      Re: microFORTH "HAA" <someone@microsoft.com> - 2017-05-01 11:15 +1000
  Re: microFORTH David Schultz <abuse@127.0.0.1> - 2017-04-30 15:02 -0500
    Re: microFORTH rickman <gnuarm@gmail.com> - 2017-04-30 21:13 -0400
      Re: microFORTH David Schultz <abuse@127.0.0.1> - 2017-04-30 20:24 -0500
        Re: microFORTH rickman <gnuarm@gmail.com> - 2017-05-01 21:02 -0400
          Re: microFORTH Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-05-02 05:58 -0400
          Re: microFORTH Coos Haak <htrofhc@gmail.com> - 2017-05-02 15:13 +0200
            Re: microFORTH rickman <gnuarm@gmail.com> - 2017-05-02 11:44 -0400
              Re: microFORTH David Schultz <abuse@127.0.0.1> - 2017-05-04 16:54 -0500
    Re: microFORTH "HAA" <someone@microsoft.com> - 2017-05-02 10:36 +1000
      Re: microFORTH "Elizabeth D. Rather" <erather@forth.com> - 2017-05-01 15:20 -1000
        Re: microFORTH "HAA" <someone@microsoft.com> - 2017-05-02 13:01 +1000
          Re: microFORTH hughaguilar96@gmail.com - 2017-05-01 20:42 -0700
            Re: microFORTH hughaguilar96@gmail.com - 2017-05-01 21:27 -0700
              Re: microFORTH "HAA" <someone@microsoft.com> - 2017-05-02 17:05 +1000
                Re: microFORTH "Elizabeth D. Rather" <erather@forth.com> - 2017-05-01 21:18 -1000
          Re: microFORTH "HAA" <someone@microsoft.com> - 2017-05-02 16:45 +1000
          Re: microFORTH JUERGEN <epldfpga@aol.com> - 2017-05-02 00:08 -0700
          Re: microFORTH hughaguilar96@gmail.com - 2017-05-02 11:36 -0700
            Re: microFORTH "HAA" <someone@microsoft.com> - 2017-05-03 10:43 +1000
              Re: microFORTH hughaguilar96@gmail.com - 2017-05-02 19:45 -0700
              Re: microFORTH Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-03 04:41 -0500
              Re: microFORTH David Schultz <abuse@127.0.0.1> - 2017-05-04 17:03 -0500
                Re: microFORTH "Elizabeth D. Rather" <erather@forth.com> - 2017-05-04 12:58 -1000
                Re: microFORTH "HAA" <someone@microsoft.com> - 2017-05-05 12:57 +1000
        Re: microFORTH David Schultz <abuse@127.0.0.1> - 2017-05-04 16:57 -0500
    Re: microFORTH Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-02 04:11 -0500
      Re: microFORTH Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-02 04:16 -0500
      Re: microFORTH Howerd <howerdo@yahoo.co.uk> - 2017-05-02 05:25 -0700
        Re: microFORTH "Elizabeth D. Rather" <erather@forth.com> - 2017-05-02 10:07 -1000
      Re: microFORTH David Schultz <abuse@127.0.0.1> - 2017-05-04 17:15 -0500

csiph-web