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

Groups > comp.lang.forth > #56977

Re: wina64 : a 64 bit native MS-Windows Forth in beta

Show all headers | View raw

On 4/9/2017 6:43 AM, Albert van der Horst wrote:
> In article <occfne$61v$1@dont-email.me>, rickman  <gnuarm@gmail.com> wrote:
>> On 4/8/2017 5:44 PM, Albert van der Horst wrote:
>>> In article <ocb69s$mg2$1@dont-email.me>, rickman  <gnuarm@gmail.com> wrote:
>>>> On 4/8/2017 3:14 AM, Albert van der Horst wrote:
>>>>> A beta version can be found via
>>>>> http://home.hccnet.nl/a.w.m.van.der.horst/ciforth.html#DOWNLOADS
>>>>>
>>>>> If nobody reports embarrassing problems it shortly will be pushed to
>>>>>     https://github.com/albertvanderhorst/ciforth
>>>>> and after more testing a 6.0.0 release will be available in
>>>>>     https://github.com/albertvanderhorst/ciforth/release
>>>>>
>>>>> The usual ciforth features:
>>>>> GPL/LGPL, runtime: one executable and one library, complete specific
>>>>> documentation, compiles to native exe files, one assembler source
>>>>> file.
>>>>>
>>>>> NOTE: KEY and KEY? may not be fully functional. SYSTEM works
>>>>> SAVE-SYSTEM has not been adequately tested because of virus checkers
>>>>> that immediately delete the generated .EXE files.
>>>>>
>>>>> Groetjes Albert
>>>>>
>>>>> 1] Despite the name kernel32.dll is 64 bits software.
>>>>
>>>> Perhaps I don't understand what "native" means.  I thought that would be
>>>> a Forth that doesn't use an operating system.  Obviously that isn't
>>>> true.  What does "native" mean?
>>>
>>> Read the description and associate that with native in a ciforth context.
>>>
>>> In 2000 I had 2 configurations for a Linux Forth, one with c-calls
>>> for KEY and EMIT and READ-BLOCK and one native, i.e. direct Linux
>>> system calls. That stuck. Then there were similar MS-DOS and MS-Windows
>>> Forth's.
>>
>> I'm sorry, I don't follow what you are saying.  What is a c-call for
>> KEY/EMIT?  I'm lost here.
>
> It means:
>
> The assembler file contains
> -----------------
> ;  ***********
> ;  *   KEY   *
> ;  ***********
> ;
> N_KEY:
>         DC      3
>         DB      "KEY"
> KEY:
>         DC    KEY+HEADSIZE
>         DC    KEY+HEADSIZE
>         DC    0x0
>         DC    ACCEP
>         DC    N_KEY
>
>         CALL    c_key    ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>         PUSH    EAX
>         JMP NEXT
> ;
> ----------------
>
> A c-file contains
> -------------
>
> /* KEY */
> int c_key( void )     /* <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< */
> {
>   char key;
>   int i;
>   tty_keymode(&std_in);
>   i=read(0, &key, 1);
>   return key;
> }
>
> -----------
>
> Then the c-file is compiled using a c-compiler and the
> object is linked to the main assembler file.
>
> What else could it mean for Pete's sake?

I don't really know why you are talking about c-calls and Linux and now 
you are bringing Pete into it.

Why can't you just explain what you mean by "native" rather than trying 
to talk about all sorts of things that just complicate the picture?  Can 
you just give a definition of "native"?  Maybe in 20 words or less?


> All xxna versions, say normal versions, of ciforth contain a place
> where it says in the one assembler source file:
> -------------------------
>
> ;  ***********
> ;  *   KEY   *
> ;  ***********
> ;
>         ALIGN    8
> N_KEY:
>         DQ      3
>         DB      "KEY"
>         ALIGN    8
> KEY:
>         DQ    DOCOL
>         DQ    KEY+HEADSIZE
>         DQ    0x0
>         DQ    PACCEP
>         DQ    N_KEY
>         DQ    0
>         DQ    0
>
>         DQ      ONE, LIT, RAWIO, STTERM ; Do not wait for CR
>         DQ      ZERO, SPFET     ; Expect single key on stack
>         DQ      ZERO            ; Standard input
>         DQ      SWAP, ONE       ; Buffer and length
>         DQ      LIT, read, XOS
>         DQ      LDUP, QERRUR
>         DQ      ZEQU, LIT, -EPIPE, LAND, QERRUR ; Presumably end of pipe.
>         DQ      ONE, LIT, RAWIO, STTERM       ; Toggle back
>         DQ      SEMIS
> ;
>
> ---------------------
> (This is in fact Forth source code, inspectable by SEE).

Why would I want to inspect source code?  Is that the only way to 
understand what you are talking about?

-- 

Rick C

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

Thread

wina64 : a 64 bit native MS-Windows Forth in beta albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-04-08 09:14 +0200
  Re: wina64 : a 64 bit native MS-Windows Forth in beta albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-04-08 09:29 +0200
  Re: wina64 : a 64 bit native MS-Windows Forth in beta "HAA" <someone@microsoft.com> - 2017-04-08 21:04 +1000
  Re: wina64 : a 64 bit native MS-Windows Forth in beta rickman <gnuarm@gmail.com> - 2017-04-08 13:26 -0400
    Re: wina64 : a 64 bit native MS-Windows Forth in beta albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-04-08 23:44 +0200
      Re: wina64 : a 64 bit native MS-Windows Forth in beta rickman <gnuarm@gmail.com> - 2017-04-09 01:13 -0400
        Re: wina64 : a 64 bit native MS-Windows Forth in beta albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-04-09 12:43 +0200
          Re: wina64 : a 64 bit native MS-Windows Forth in beta minforth@arcor.de - 2017-04-09 04:31 -0700
            Re: wina64 : a 64 bit native MS-Windows Forth in beta john <anon@example.com> - 2017-04-09 13:13 +0100
            Re: wina64 : a 64 bit native MS-Windows Forth in beta albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-04-09 14:43 +0200
              Re: wina64 : a 64 bit native MS-Windows Forth in beta minforth@arcor.de - 2017-04-09 08:56 -0700
                Re: wina64 : a 64 bit native MS-Windows Forth in beta foxaudioresearch@gmail.com - 2017-04-09 09:44 -0700
                Re: wina64 : a 64 bit native MS-Windows Forth in beta minforth@arcor.de - 2017-04-09 22:07 -0700
                Re: wina64 : a 64 bit native MS-Windows Forth in beta albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-04-10 12:40 +0200
          Re: wina64 : a 64 bit native MS-Windows Forth in beta rickman <gnuarm@gmail.com> - 2017-04-10 02:15 -0400
            Re: wina64 : a 64 bit native MS-Windows Forth in beta Julian Fondren <julian.fondren@gmail.com> - 2017-04-09 23:21 -0700
              Re: wina64 : a 64 bit native MS-Windows Forth in beta Paul Rubin <no.email@nospam.invalid> - 2017-04-10 01:40 -0700
                Re: wina64 : a 64 bit native MS-Windows Forth in beta Julian Fondren <julian.fondren@gmail.com> - 2017-04-10 04:15 -0700
                Re: wina64 : a 64 bit native MS-Windows Forth in beta albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-04-10 13:49 +0200
              Re: wina64 : a 64 bit native MS-Windows Forth in beta rickman <gnuarm@gmail.com> - 2017-04-10 10:05 -0400
                Re: wina64 : a 64 bit native MS-Windows Forth in beta anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-04-10 14:27 +0000
                Re: wina64 : a 64 bit native MS-Windows Forth in beta albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-04-10 20:05 +0200
                Re: wina64 : a 64 bit native MS-Windows Forth in beta minforth@arcor.de - 2017-04-10 14:26 -0700

csiph-web