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


Groups > comp.lang.forth > #58689

Re: microFORTH

From "HAA" <someone@microsoft.com>
Newsgroups comp.lang.forth
Subject Re: microFORTH
Date 2017-05-05 12:57 +1000
Organization Aioe.org NNTP Server
Message-ID <oegpov$kgo$1@gioia.aioe.org> (permalink)
References <2d438ef9-36ec-42b6-b98f-792dcc3798db@googlegroups.com><a_WdnQAWBNxR35vEnZ2dnUU7-WXNnZ2d@earthlink.com><oe8kb5$uam$1@gioia.aioe.org><qcmdncwmT_l6Q5rEnZ2dnUU7-I_NnZ2d@supernews.com><oe8sr5$182s$1@gioia.aioe.org><cc5a089a-f28f-4d9d-85d1-3f7010416536@googlegroups.com><oeb94b$1crp$1@gioia.aioe.org> <u-2dnbydu4m3OJbEnZ2dnUU7-KfNnZ2d@earthlink.com>

Show all headers | View raw


David Schultz wrote:
> On 05/02/2017 07:43 PM, HAA wrote:
>
> > There's no bug.  When referencing a disk block, BLK is 16 bits.
> > However as BLK and IN represent 3 contiguous bytes, a mix of
> > C@ C! ! @ were needed to save/restore/zero both BLK and IN.
> >
>
> How does that work?
>
> If BLK is zero then input is from the terminal. This implies that the
> high byte of IN is also zero. Which would be fine.
>
> But if BLK is non-zero then IN cannot be used as is to index into the
> block. Something else must be done. It could be as simple as "IN 1+ C@"
> but that means that the code to interpret a disk block is different from
> the code to interpret a line from the terminal.

QUIT suggests TIB is 80 chars in which case BLK= 16 bits, IN= 8 bits
would work without fuss.  There must however be an 'other' reason IN
was defined as a 16 bit entry (Appendix A Tech Manual).

>
> Kind of making that saving one byte of user variable storage moot.

microFORTH is like SwiftX in that target apps will likely never use
BLK IN WORD BLOCK etc (the code for these don't reside in the
nucleus).  You then have an incentive to keep user area to a
minimum e.g. BASE is 1 byte.

>
> Of course if ALL of the code were present we could see how it is done.

That or a disk dump.  Addresses for the nucleus routines 00-01FF are
given in screens 51/52.  Headers, interpreter and other code will be
residing elsewhere.




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