Lower case is used for Locals.
{ a 2b - c 2d - e f -1, 0 }
a, 32b input
2b, 64b input (double)
c, 32b temporary
2d, 64b temporary
e, f, outputs
-1, output available flag
0, no output flag

44 -> c, store 44 in c
AT a, pointer to first local

Comments?

In article <eb89ae7c-d176-4cf2-bb5f-182accc66047n@googlegroups.com>,
John Hart <johnrogerhart@gmail.com> wrote:
>Lower case is used for Locals.
>{ a 2b - c 2d - e f -1, 0 }
>a, 32b input
>2b, 64b input (double)
>c, 32b temporary
>2d, 64b temporary
>e, f, outputs
>-1, output available flag
>0, no output flag
>
>44 -> c, store 44 in c
>AT a, pointer to first local
>
>Comments?

Puzzled.

Groetjes Albert
--
Don't praise the day before the evening. One swallow doesn't make spring.
You must not say "hey" before you have crossed the bridge. Don't sell the
hide of the bear until you shot it. Better one bird in the hand than ten in
the air. First gain is a cat spinning. - the Wise from Antrim -

On Wed, 10 May 2023 16:51:58 -0700 (PDT)
John Hart <johnrogerhart@gmail.com> wrote:

> Lower case is used for Locals.
> { a 2b - c 2d - e f -1, 0 }
> a, 32b input
> 2b, 64b input (double)
> c, 32b temporary
> 2d, 64b temporary
> e, f, outputs
> -1, output available flag
> 0, no output flag
> 44 -> c, store 44 in c
> AT a, pointer to first local
>
> Comments?

Do the "-1," and "0" map onto "e" and "f"?

Jan Coombs
--

On Thursday, May 11, 2023 at 2:03:54 AM UTC-7, none albert wrote:
> In article <eb89ae7c-d176-4cf2...@googlegroups.com>,
> John Hart <johnro...@gmail.com> wrote:
> >Lower case is used for Locals.
> >{ a 2b - c 2d - e f -1, 0 }
> >a, 32b input
> >2b, 64b input (double)
> >c, 32b temporary
> >2d, 64b temporary
> >e, f, outputs
> >-1, output available flag
> >0, no output flag
> >
> >44 -> c, store 44 in c
> >AT a, pointer to first local
> >
> >Comments?
> Puzzled.
Is this the standard local syntax?

On Thursday, May 11, 2023 at 2:26:35 AM UTC-7, Jan Coombs wrote:
> On Wed, 10 May 2023 16:51:58 -0700 (PDT)
> John Hart <johnro...@gmail.com> wrote:
>
> > Lower case is used for Locals.
> > { a 2b - c 2d - e f -1, 0 }
> > a, 32b input
> > 2b, 64b input (double)
> > c, 32b temporary
> > 2d, 64b temporary
> > e, f, outputs
> > -1, output available flag
> > 0, no output flag
> > 44 -> c, store 44 in c
> > AT a, pointer to first local
> >
> > Comments?
> Do the "-1," and "0" map onto "e" and "f"?

0 means no output, -1 means there is output in this case when conditional output is used.
When a search fails there's no reason to return a pointer.
Returning a -1 for not found eliminates the need for conditional outputs,
but will require a DUP and a DROP, so a success flag is a better way to impliment search functions.
Outputs in the expression are comments, not checked at compile or runtime, but they could be.

jrh

On Wednesday, May 10, 2023 at 4:51:59 PM UTC-7, John Hart wrote:
> Lower case is used for Locals.
> { a 2b - c 2d - e f -1, 0 }
> a, 32b input
> 2b, 64b input (double)
> c, 32b temporary
> 2d, 64b temporary
> e, f, outputs
> -1, output available flag
> 0, no output flag
>
> 44 -> c, store 44 in c
> AT a, pointer to first local
>
> Comments?

You seem to be trying to implement local variables with data-types.
This is a bad idea. Various people have tried to turn Forth into a typed
language similar to Pascal and this has never worked out well.
I would not do this. This is just the latest in your lengthy series of bad ideas.

I had local variables working in MFX back in 1995.
Are you trying to insult me be implying that I didn't have local variables in MFX?

The story is that, I wrote MFX for the purpose of supporting the motion-control
program. This succeeded. The MiniForth ran the laser-etcher. MFX didn't have locals
because the motion-control program was ported from the LMI 80c320
cross-compiler that didn't have locals, so the motion-control program didn't
use locals. You told me that my next project would be to write a C compiler for
the MiniForth, because most customers want C, although you had no intention
of ever writing C code for the MiniForth yourself because you only know Forth
and you were okay with MFX. So I bought a book (my own money) on LCC and
began reading up on how to write a C compiler. I also asked for an upgrade to
the MiniForth to support local variables. The MiniForth doesn't have indexed
addressing, so a traditional local-frame was not realistic. You provided 16 fast
memory locations in the bottom of data-memory. I implemented 16 local variables
in these fast locations and I would move the whole block to a stack upon function
entrance, then move the block back upon function exit to restore for the parent
function. This is the same technique that is used in 8032 C compilers because
the 8032 doesn't have indexed addressing either. I wrote a lot of ghost functions
to support local variables. For example, I had post-increment, pre-increment,
post-decrement, and pre-decrement for the locals. There were hundreds of
ghost functions using the local variables in various ways.

Ghost functions didn't "materialize" until they were first referenced. I could have
hundreds of ghost functions but none of them used any code-memory unless they
were actually referenced in the Forth program, whereupon they would be compiled
into code-memory, and any later reference would use this compiled code too.
There was only 64KW of code-memory available, so I had to not fill it up with code
that never gets used. I could provide ghost functions for all 16 local variables,
but most programs would never have any functions that used all 16 local variables,
so the code supporting the upper locals would never materialize and take up room
in code-memory.

C actually requires support for 32 local variables, so I couldn't be fully C compatible.
LCC is really designed for a processor with 32 registers, such as the MIPS, etc..
I only had 16 fast locations in memory. I considered using only 8 of these for locals,
and leave the other 8 for pseudo-registers. This would be roughly comparable to the
8086 that also has only 8 registers. This would not work for LCC though because it
is designed for more modern processors with a lot of registers. All in all, I was very
unenthusiastic about writing a C compiler for the MiniForth. I expected that it was
going to generate slow inefficient code because the MiniForth is really designed to
support Forth, not C. Everybody in the world would say that this proves that I'm
utterly incompetent. Nobody would consider MFX to be a good Forth compiler, but
everybody would consider MFX to be a bad C compiler written by an incompetent.
You were telling me that you expected the C compiler to be written fairly quickly
because you weren't willing to spend a lot of money on it, and because I hadn't
made any progress on the C compiler other than implementing local variables
in MFX, you considered me to be incompetent as a C programmer. I left Testra
because of this. You had never praised me for writing MFX, and you weren't providing
me with health insurance although Steve Brault got health insurance, and Tom Hart
told me clearly that I would never get a raise in pay. So I left. I still expected to get
a reference for writing MFX, but I later heard you (or Tom Hart impersonating you)
on a speaker phone saying that I had accomplished nothing and I was not eligible
for rehire. Now three decades later though, you admit for the first time that I did
write MFX and that you still rely on MFX at Testra. Why didn't you admit this in 1995?

On Saturday, 13 May 2023 at 21:30:55 UTC+1, Hugh Aguilar wrote:
> On Wednesday, May 10, 2023 at 4:51:59 PM UTC-7, John Hart wrote:
> > Lower case is used for Locals.
> > { a 2b - c 2d - e f -1, 0 }
> > a, 32b input
> > 2b, 64b input (double)
> > c, 32b temporary
> > 2d, 64b temporary
> > e, f, outputs
> > -1, output available flag
> > 0, no output flag
> >
> > 44 -> c, store 44 in c
> > AT a, pointer to first local
> >
> > Comments?
> You seem to be trying to implement local variables with data-types.
> This is a bad idea. Various people have tried to turn Forth into a typed
> language similar to Pascal and this has never worked out well.
> I would not do this. This is just the latest in your lengthy series of bad ideas.
>
> I had local variables working in MFX back in 1995.
> Are you trying to insult me be implying that I didn't have local variables in MFX?
>
> The story is that, I wrote MFX for the purpose of supporting the motion-control
> program. This succeeded. The MiniForth ran the laser-etcher. MFX didn't have locals
> because the motion-control program was ported from the LMI 80c320
> cross-compiler that didn't have locals, so the motion-control program didn't
> use locals. You told me that my next project would be to write a C compiler for
> the MiniForth, because most customers want C, although you had no intention
> of ever writing C code for the MiniForth yourself because you only know Forth
> and you were okay with MFX. So I bought a book (my own money) on LCC and
> began reading up on how to write a C compiler. I also asked for an upgrade to
> the MiniForth to support local variables. The MiniForth doesn't have indexed
> addressing, so a traditional local-frame was not realistic. You provided 16 fast
> memory locations in the bottom of data-memory. I implemented 16 local variables
> in these fast locations and I would move the whole block to a stack upon function
> entrance, then move the block back upon function exit to restore for the parent
> function. This is the same technique that is used in 8032 C compilers because
> the 8032 doesn't have indexed addressing either. I wrote a lot of ghost functions
> to support local variables. For example, I had post-increment, pre-increment,
> post-decrement, and pre-decrement for the locals. There were hundreds of
> ghost functions using the local variables in various ways.
>
> Ghost functions didn't "materialize" until they were first referenced. I could have
> hundreds of ghost functions but none of them used any code-memory unless they
> were actually referenced in the Forth program, whereupon they would be compiled
> into code-memory, and any later reference would use this compiled code too.
> There was only 64KW of code-memory available, so I had to not fill it up with code
> that never gets used. I could provide ghost functions for all 16 local variables,
> but most programs would never have any functions that used all 16 local variables,
> so the code supporting the upper locals would never materialize and take up room
> in code-memory.
>
> C actually requires support for 32 local variables, so I couldn't be fully C compatible.
> LCC is really designed for a processor with 32 registers, such as the MIPS, etc..
> I only had 16 fast locations in memory. I considered using only 8 of these for locals,
> and leave the other 8 for pseudo-registers. This would be roughly comparable to the
> 8086 that also has only 8 registers. This would not work for LCC though because it
> is designed for more modern processors with a lot of registers. All in all, I was very
> unenthusiastic about writing a C compiler for the MiniForth. I expected that it was
> going to generate slow inefficient code because the MiniForth is really designed to
> support Forth, not C. Everybody in the world would say that this proves that I'm
> utterly incompetent. Nobody would consider MFX to be a good Forth compiler, but
> everybody would consider MFX to be a bad C compiler written by an incompetent.
> You were telling me that you expected the C compiler to be written fairly quickly
> because you weren't willing to spend a lot of money on it, and because I hadn't
> made any progress on the C compiler other than implementing local variables
> in MFX, you considered me to be incompetent as a C programmer. I left Testra
> because of this. You had never praised me for writing MFX, and you weren't providing
> me with health insurance although Steve Brault got health insurance, and Tom Hart
> told me clearly that I would never get a raise in pay. So I left. I still expected to get
> a reference for writing MFX, but I later heard you (or Tom Hart impersonating you)
> on a speaker phone saying that I had accomplished nothing and I was not eligible
> for rehire. Now three decades later though, you admit for the first time that I did
> write MFX and that you still rely on MFX at Testra. Why didn't you admit this in 1995?

It seems you memories are fading.
Have a look here for
WHAT HAPPENED AT TESTRA:
https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0/m/mvVy-GN7AwAJ

But does it really matter?
John Hart is posting interesting information one generation later.

You gave a monkeys about such a project for 30 years now. Did not share anything.
10 000 times you woke up and decided
- I will not tell anybody about this project,
just concentate on concentrated agression and lies..

I am looking forward to more interesting information from John,

On Sunday, May 14, 2023 at 3:30:15 AM UTC-4, Jurgen Pitaske wrote:
> On Saturday, 13 May 2023 at 21:30:55 UTC+1, Hugh Aguilar wrote:
> > On Wednesday, May 10, 2023 at 4:51:59 PM UTC-7, John Hart wrote:
> > > Lower case is used for Locals.
> > > { a 2b - c 2d - e f -1, 0 }
> > > a, 32b input
> > > 2b, 64b input (double)
> > > c, 32b temporary
> > > 2d, 64b temporary
> > > e, f, outputs
> > > -1, output available flag
> > > 0, no output flag
> > >
> > > 44 -> c, store 44 in c
> > > AT a, pointer to first local
> > >
> > > Comments?
> > You seem to be trying to implement local variables with data-types.
> > This is a bad idea. Various people have tried to turn Forth into a typed
> > language similar to Pascal and this has never worked out well.
> > I would not do this. This is just the latest in your lengthy series of bad ideas.
> >
> > I had local variables working in MFX back in 1995.
> > Are you trying to insult me be implying that I didn't have local variables in MFX?
> >
> > The story is that, I wrote MFX for the purpose of supporting the motion-control
> > program. This succeeded. The MiniForth ran the laser-etcher. MFX didn't have locals
> > because the motion-control program was ported from the LMI 80c320
> > cross-compiler that didn't have locals, so the motion-control program didn't
> > use locals. You told me that my next project would be to write a C compiler for
> > the MiniForth, because most customers want C, although you had no intention
> > of ever writing C code for the MiniForth yourself because you only know Forth
> > and you were okay with MFX. So I bought a book (my own money) on LCC and
> > began reading up on how to write a C compiler. I also asked for an upgrade to
> > the MiniForth to support local variables. The MiniForth doesn't have indexed
> > addressing, so a traditional local-frame was not realistic. You provided 16 fast
> > memory locations in the bottom of data-memory. I implemented 16 local variables
> > in these fast locations and I would move the whole block to a stack upon function
> > entrance, then move the block back upon function exit to restore for the parent
> > function. This is the same technique that is used in 8032 C compilers because
> > the 8032 doesn't have indexed addressing either. I wrote a lot of ghost functions
> > to support local variables. For example, I had post-increment, pre-increment,
> > post-decrement, and pre-decrement for the locals. There were hundreds of
> > ghost functions using the local variables in various ways.
> >
> > Ghost functions didn't "materialize" until they were first referenced. I could have
> > hundreds of ghost functions but none of them used any code-memory unless they
> > were actually referenced in the Forth program, whereupon they would be compiled
> > into code-memory, and any later reference would use this compiled code too.
> > There was only 64KW of code-memory available, so I had to not fill it up with code
> > that never gets used. I could provide ghost functions for all 16 local variables,
> > but most programs would never have any functions that used all 16 local variables,
> > so the code supporting the upper locals would never materialize and take up room
> > in code-memory.
> >
> > C actually requires support for 32 local variables, so I couldn't be fully C compatible.
> > LCC is really designed for a processor with 32 registers, such as the MIPS, etc..
> > I only had 16 fast locations in memory. I considered using only 8 of these for locals,
> > and leave the other 8 for pseudo-registers. This would be roughly comparable to the
> > 8086 that also has only 8 registers. This would not work for LCC though because it
> > is designed for more modern processors with a lot of registers. All in all, I was very
> > unenthusiastic about writing a C compiler for the MiniForth. I expected that it was
> > going to generate slow inefficient code because the MiniForth is really designed to
> > support Forth, not C. Everybody in the world would say that this proves that I'm
> > utterly incompetent. Nobody would consider MFX to be a good Forth compiler, but
> > everybody would consider MFX to be a bad C compiler written by an incompetent.
> > You were telling me that you expected the C compiler to be written fairly quickly
> > because you weren't willing to spend a lot of money on it, and because I hadn't
> > made any progress on the C compiler other than implementing local variables
> > in MFX, you considered me to be incompetent as a C programmer. I left Testra
> > because of this. You had never praised me for writing MFX, and you weren't providing
> > me with health insurance although Steve Brault got health insurance, and Tom Hart
> > told me clearly that I would never get a raise in pay. So I left. I still expected to get
> > a reference for writing MFX, but I later heard you (or Tom Hart impersonating you)
> > on a speaker phone saying that I had accomplished nothing and I was not eligible
> > for rehire. Now three decades later though, you admit for the first time that I did
> > write MFX and that you still rely on MFX at Testra. Why didn't you admit this in 1995?
> It seems you memories are fading.
> Have a look here for
> WHAT HAPPENED AT TESTRA:
> https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0/m/mvVy-GN7AwAJ
>
> But does it really matter?
> John Hart is posting interesting information one generation later.
>
> You gave a monkeys about such a project for 30 years now. Did not share anything.
> 10 000 times you woke up and decided
> - I will not tell anybody about this project,
> just concentate on concentrated agression and lies..
>
> I am looking forward to more interesting information from John,

Then why are you talking to Hugh? Do you ever get anything useful from such discourse?

I should ask myself why I try to talk to you about talking to Hugh. Most people know not to engage him. I don't know why I try to get through to you about this. I guess I have the same mental illness as you.

--

Rick C.

- Get 1,000 miles of free Supercharging
- Tesla referral code - https://ts.la/richard11209

On Monday, 15 May 2023 at 08:18:10 UTC+1, Lorem Ipsum wrote:
> On Sunday, May 14, 2023 at 3:30:15 AM UTC-4, Jurgen Pitaske wrote:
> > On Saturday, 13 May 2023 at 21:30:55 UTC+1, Hugh Aguilar wrote:
> > > On Wednesday, May 10, 2023 at 4:51:59 PM UTC-7, John Hart wrote:
> > > > Lower case is used for Locals.
> > > > { a 2b - c 2d - e f -1, 0 }
> > > > a, 32b input
> > > > 2b, 64b input (double)
> > > > c, 32b temporary
> > > > 2d, 64b temporary
> > > > e, f, outputs
> > > > -1, output available flag
> > > > 0, no output flag
> > > >
> > > > 44 -> c, store 44 in c
> > > > AT a, pointer to first local
> > > >
> > > > Comments?
> > > You seem to be trying to implement local variables with data-types.
> > > This is a bad idea. Various people have tried to turn Forth into a typed
> > > language similar to Pascal and this has never worked out well.
> > > I would not do this. This is just the latest in your lengthy series of bad ideas.
> > >
> > > I had local variables working in MFX back in 1995.
> > > Are you trying to insult me be implying that I didn't have local variables in MFX?
> > >
> > > The story is that, I wrote MFX for the purpose of supporting the motion-control
> > > program. This succeeded. The MiniForth ran the laser-etcher. MFX didn't have locals
> > > because the motion-control program was ported from the LMI 80c320
> > > cross-compiler that didn't have locals, so the motion-control program didn't
> > > use locals. You told me that my next project would be to write a C compiler for
> > > the MiniForth, because most customers want C, although you had no intention
> > > of ever writing C code for the MiniForth yourself because you only know Forth
> > > and you were okay with MFX. So I bought a book (my own money) on LCC and
> > > began reading up on how to write a C compiler. I also asked for an upgrade to
> > > the MiniForth to support local variables. The MiniForth doesn't have indexed
> > > addressing, so a traditional local-frame was not realistic. You provided 16 fast
> > > memory locations in the bottom of data-memory. I implemented 16 local variables
> > > in these fast locations and I would move the whole block to a stack upon function
> > > entrance, then move the block back upon function exit to restore for the parent
> > > function. This is the same technique that is used in 8032 C compilers because
> > > the 8032 doesn't have indexed addressing either. I wrote a lot of ghost functions
> > > to support local variables. For example, I had post-increment, pre-increment,
> > > post-decrement, and pre-decrement for the locals. There were hundreds of
> > > ghost functions using the local variables in various ways.
> > >
> > > Ghost functions didn't "materialize" until they were first referenced.. I could have
> > > hundreds of ghost functions but none of them used any code-memory unless they
> > > were actually referenced in the Forth program, whereupon they would be compiled
> > > into code-memory, and any later reference would use this compiled code too.
> > > There was only 64KW of code-memory available, so I had to not fill it up with code
> > > that never gets used. I could provide ghost functions for all 16 local variables,
> > > but most programs would never have any functions that used all 16 local variables,
> > > so the code supporting the upper locals would never materialize and take up room
> > > in code-memory.
> > >
> > > C actually requires support for 32 local variables, so I couldn't be fully C compatible.
> > > LCC is really designed for a processor with 32 registers, such as the MIPS, etc..
> > > I only had 16 fast locations in memory. I considered using only 8 of these for locals,
> > > and leave the other 8 for pseudo-registers. This would be roughly comparable to the
> > > 8086 that also has only 8 registers. This would not work for LCC though because it
> > > is designed for more modern processors with a lot of registers. All in all, I was very
> > > unenthusiastic about writing a C compiler for the MiniForth. I expected that it was
> > > going to generate slow inefficient code because the MiniForth is really designed to
> > > support Forth, not C. Everybody in the world would say that this proves that I'm
> > > utterly incompetent. Nobody would consider MFX to be a good Forth compiler, but
> > > everybody would consider MFX to be a bad C compiler written by an incompetent.
> > > You were telling me that you expected the C compiler to be written fairly quickly
> > > because you weren't willing to spend a lot of money on it, and because I hadn't
> > > made any progress on the C compiler other than implementing local variables
> > > in MFX, you considered me to be incompetent as a C programmer. I left Testra
> > > because of this. You had never praised me for writing MFX, and you weren't providing
> > > me with health insurance although Steve Brault got health insurance, and Tom Hart
> > > told me clearly that I would never get a raise in pay. So I left. I still expected to get
> > > a reference for writing MFX, but I later heard you (or Tom Hart impersonating you)
> > > on a speaker phone saying that I had accomplished nothing and I was not eligible
> > > for rehire. Now three decades later though, you admit for the first time that I did
> > > write MFX and that you still rely on MFX at Testra. Why didn't you admit this in 1995?
> > It seems you memories are fading.
> > Have a look here for
> > WHAT HAPPENED AT TESTRA:
> > https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0/m/mvVy-GN7AwAJ
> >
> > But does it really matter?
> > John Hart is posting interesting information one generation later.
> >
> > You gave a monkeys about such a project for 30 years now. Did not share anything.
> > 10 000 times you woke up and decided
> > - I will not tell anybody about this project,
> > just concentate on concentrated agression and lies..
> >
> > I am looking forward to more interesting information from John,
> Then why are you talking to Hugh? Do you ever get anything useful from such discourse?
>
> I should ask myself why I try to talk to you about talking to Hugh. Most people know not to engage him. I don't know why I try to get through to you about this. I guess I have the same mental illness as you.
>
> --
>
> Rick C.
>
> - Get 1,000 miles of free Supercharging
> - Tesla referral code - https://ts.la/richard11209

I post when I feel like.
He has been agressive enough against me and MPE when I was working for them..
This is now for more than 10 years.

This Forth Killer will not stop until he dies.
But at least others should know, and not everybody should let him piss off everybody
and make people move away from here and from Forth.
..
The WHAT HAPPENED AT TESTRA was one of the best posts I ever started.
More people read this than any other post I have seen here.
So they know now.

Why you waste everybodies time with such a post of yours I do not understand.
But there we are.
This had been discussed here many many times before.

On Saturday, May 13, 2023 at 1:30:55 PM UTC-7, Hugh Aguilar wrote:
> I wrote a lot of ghost functions
> to support local variables. For example, I had post-increment, pre-increment,
> post-decrement, and pre-decrement for the locals. There were hundreds of
> ghost functions using the local variables in various ways.
>
> Ghost functions didn't "materialize" until they were first referenced. I could have
> hundreds of ghost functions but none of them used any code-memory unless they
> were actually referenced in the Forth program, whereupon they would be compiled
> into code-memory, and any later reference would use this compiled code too.

I didn't actually hand-write hundreds of ghost functions using local variables
in various ways. I wrote macros. For example, I would write a macro to fetch a
local variable with post-increment, then I would use this macro 16 times to generate
16 ghost functions each hard-coded for a particular local variable.

I had early-binding macros in MFX roughly comparable to the early-binding macros
that I have in the novice package. This was easy to write in UR/Forth because FIND
works. In ANS-Forth, FIND is broken, so I wasn't able to write an early-binding macro
in ANS-Forth until I figured out that the disambiguifiers fixed the broken FIND
in ANS-Forth. OTOH, my macros in MFX weren't as good as my macros in ANS-Forth
because they didn't support words that extract data from the input stream (such as:
[char] S" etc.) like my macros in the novice-package do. I could have upgraded the
MFX macros to do everything that the ANS-Forth macros do, but I just never got
around to it. Testra didn't want to pay for anything that didn't directly relate to the
motion-control program, and the motion-control program was completed and working.

On Monday, May 15, 2023 at 5:45:22 AM UTC-4, Jurgen Pitaske wrote:
> On Monday, 15 May 2023 at 08:18:10 UTC+1, Lorem Ipsum wrote:
> > On Sunday, May 14, 2023 at 3:30:15 AM UTC-4, Jurgen Pitaske wrote:
> > > It seems you memories are fading.
> > > Have a look here for
> > > WHAT HAPPENED AT TESTRA:
> > > https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0/m/mvVy-GN7AwAJ
> > >
> > > But does it really matter?
> > > John Hart is posting interesting information one generation later.
> > >
> > > You gave a monkeys about such a project for 30 years now. Did not share anything.
> > > 10 000 times you woke up and decided
> > > - I will not tell anybody about this project,
> > > just concentate on concentrated agression and lies..
> > >
> > > I am looking forward to more interesting information from John,
> > Then why are you talking to Hugh? Do you ever get anything useful from such discourse?
> >
> > I should ask myself why I try to talk to you about talking to Hugh. Most people know not to engage him. I don't know why I try to get through to you about this. I guess I have the same mental illness as you.
> >
> > --
> >
> > Rick C.
> >
> > - Get 1,000 miles of free Supercharging
> > - Tesla referral code - https://ts.la/richard11209
> I post when I feel like.

Yes, exactly. You are posting very emotionally, spewing your bile across the group. I've tried to explain this to you before, but you can't comprehend that YOUR BILE is just as bad for Forth and the clf group, as HIS BILE. I've come to realize that in many ways, the two of you are cut from the same cloth. I should never bother to try to explain this to you. I have done so many times, but you shrug it off as you believe you are on a pure quest and can do no harm.

> He has been agressive enough against me and MPE when I was working for them.
> This is now for more than 10 years.

He is a nut, posting crap on the Internet. It's hard to imagine that is of any real harm to you, in any way. Ignore him, and he goes away. 99% of us here manage to do that. Why can't you?

> This Forth Killer will not stop until he dies.

You can't kill something that is already dead.

> But at least others should know, and not everybody should let him piss off everybody
> and make people move away from here and from Forth.

Wait, are you talking about Hugh, or yourself?

> The WHAT HAPPENED AT TESTRA was one of the best posts I ever started.
> More people read this than any other post I have seen here.
> So they know now.
>
> Why you waste everybodies time with such a post of yours I do not understand.

That is the funniest thing you have ever written. LOL

> But there we are.
> This had been discussed here many many times before.

Yes, and you never learn. I'm sorry I bothered you. In the future, I'll try to refrain from providing you with a view into reality.

--

Rick C.

+ Get 1,000 miles of free Supercharging
+ Tesla referral code - https://ts.la/richard11209

On Tuesday, 16 May 2023 at 18:29:54 UTC+1, Lorem Ipsum wrote:
> On Monday, May 15, 2023 at 5:45:22 AM UTC-4, Jurgen Pitaske wrote:
> > On Monday, 15 May 2023 at 08:18:10 UTC+1, Lorem Ipsum wrote:
> > > On Sunday, May 14, 2023 at 3:30:15 AM UTC-4, Jurgen Pitaske wrote:
> > > > It seems you memories are fading.
> > > > Have a look here for
> > > > WHAT HAPPENED AT TESTRA:
> > > > https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0/m/mvVy-GN7AwAJ
> > > >
> > > > But does it really matter?
> > > > John Hart is posting interesting information one generation later.
> > > >
> > > > You gave a monkeys about such a project for 30 years now. Did not share anything.
> > > > 10 000 times you woke up and decided
> > > > - I will not tell anybody about this project,
> > > > just concentate on concentrated agression and lies..
> > > >
> > > > I am looking forward to more interesting information from John,
> > > Then why are you talking to Hugh? Do you ever get anything useful from such discourse?
> > >
> > > I should ask myself why I try to talk to you about talking to Hugh. Most people know not to engage him. I don't know why I try to get through to you about this. I guess I have the same mental illness as you.
> > >
> > > --
> > >
> > > Rick C.
> > >
> > > - Get 1,000 miles of free Supercharging
> > > - Tesla referral code - https://ts.la/richard11209
> > I post when I feel like.
> Yes, exactly. You are posting very emotionally, spewing your bile across the group. I've tried to explain this to you before, but you can't comprehend that YOUR BILE is just as bad for Forth and the clf group, as HIS BILE. I've come to realize that in many ways, the two of you are cut from the same cloth. I should never bother to try to explain this to you. I have done so many times, but you shrug it off as you believe you are on a pure quest and can do no harm.
> > He has been agressive enough against me and MPE when I was working for them.
> > This is now for more than 10 years.
> He is a nut, posting crap on the Internet. It's hard to imagine that is of any real harm to you, in any way. Ignore him, and he goes away. 99% of us here manage to do that. Why can't you?
> > This Forth Killer will not stop until he dies.
> You can't kill something that is already dead.
> > But at least others should know, and not everybody should let him piss off everybody
> > and make people move away from here and from Forth.
> Wait, are you talking about Hugh, or yourself?
> > The WHAT HAPPENED AT TESTRA was one of the best posts I ever started.
> > More people read this than any other post I have seen here.
> > So they know now.
> >
> > Why you waste everybodies time with such a post of yours I do not understand.
> That is the funniest thing you have ever written. LOL
> > But there we are.
> > This had been discussed here many many times before.
> Yes, and you never learn. I'm sorry I bothered you. In the future, I'll try to refrain from providing you with a view into reality.
>
> --
>
> Rick C.
>
> + Get 1,000 miles of free Supercharging
> + Tesla referral code - https://ts.la/richard11209

How you try to sell your bullshit is just funny
- but as there is not much else here
- you will continue anyway.
Though every time you say you will not.
Very funny again.

If Forth is dead for you - why are you here?
No Wife, no friends - but CLF ?

On Tuesday, May 16, 2023 at 2:10:18 PM UTC-4, Jurgen Pitaske wrote:
> On Tuesday, 16 May 2023 at 18:29:54 UTC+1, Lorem Ipsum wrote:
> > On Monday, May 15, 2023 at 5:45:22 AM UTC-4, Jurgen Pitaske wrote:
> > > On Monday, 15 May 2023 at 08:18:10 UTC+1, Lorem Ipsum wrote:
> > > > On Sunday, May 14, 2023 at 3:30:15 AM UTC-4, Jurgen Pitaske wrote:
> > > > > It seems you memories are fading.
> > > > > Have a look here for
> > > > > WHAT HAPPENED AT TESTRA:
> > > > > https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0/m/mvVy-GN7AwAJ
> > > > >
> > > > > But does it really matter?
> > > > > John Hart is posting interesting information one generation later..
> > > > >
> > > > > You gave a monkeys about such a project for 30 years now. Did not share anything.
> > > > > 10 000 times you woke up and decided
> > > > > - I will not tell anybody about this project,
> > > > > just concentate on concentrated agression and lies..
> > > > >
> > > > > I am looking forward to more interesting information from John,
> > > > Then why are you talking to Hugh? Do you ever get anything useful from such discourse?
> > > >
> > > > I should ask myself why I try to talk to you about talking to Hugh. Most people know not to engage him. I don't know why I try to get through to you about this. I guess I have the same mental illness as you.
> > > >
> > > > --
> > > >
> > > > Rick C.
> > > >
> > > > - Get 1,000 miles of free Supercharging
> > > > - Tesla referral code - https://ts.la/richard11209
> > > I post when I feel like.
> > Yes, exactly. You are posting very emotionally, spewing your bile across the group. I've tried to explain this to you before, but you can't comprehend that YOUR BILE is just as bad for Forth and the clf group, as HIS BILE.. I've come to realize that in many ways, the two of you are cut from the same cloth. I should never bother to try to explain this to you. I have done so many times, but you shrug it off as you believe you are on a pure quest and can do no harm.
> > > He has been agressive enough against me and MPE when I was working for them.
> > > This is now for more than 10 years.
> > He is a nut, posting crap on the Internet. It's hard to imagine that is of any real harm to you, in any way. Ignore him, and he goes away. 99% of us here manage to do that. Why can't you?
> > > This Forth Killer will not stop until he dies.
> > You can't kill something that is already dead.
> > > But at least others should know, and not everybody should let him piss off everybody
> > > and make people move away from here and from Forth.
> > Wait, are you talking about Hugh, or yourself?
> > > The WHAT HAPPENED AT TESTRA was one of the best posts I ever started.
> > > More people read this than any other post I have seen here.
> > > So they know now.
> > >
> > > Why you waste everybodies time with such a post of yours I do not understand.
> > That is the funniest thing you have ever written. LOL
> > > But there we are.
> > > This had been discussed here many many times before.
> > Yes, and you never learn. I'm sorry I bothered you. In the future, I'll try to refrain from providing you with a view into reality.
> >
> > --
> >
> > Rick C.
> >
> > + Get 1,000 miles of free Supercharging
> > + Tesla referral code - https://ts.la/richard11209
> How you try to sell your bullshit is just funny
> - but as there is not much else here
> - you will continue anyway.
> Though every time you say you will not.
> Very funny again.
>
> If Forth is dead for you - why are you here?
> No Wife, no friends - but CLF ?

Yes, I think of clf as my wife. I guess it is your mistress. Should I be jealous?

You have to admit, you are good material for any stand up comedian. I think in all the times I've tried to explain to you how your vitriolic posts are just as bad as anyone else's, only one time did you give up the "battle" and not respond. I call it a "battle", because that is how you have refereed to it.

Whatever, this is very thin entertainment. It's not entirely different from teasing the town fool. When others do it, it can be amusing, but it's not something I have much fun doing. Still, I'm waiting for a contract, so I do get bored.

--

Rick C.

-- Get 1,000 miles of free Supercharging
-- Tesla referral code - https://ts.la/richard11209

On Tuesday, 16 May 2023 at 23:09:18 UTC+1, Lorem Ipsum wrote:
> On Tuesday, May 16, 2023 at 2:10:18 PM UTC-4, Jurgen Pitaske wrote:
> > On Tuesday, 16 May 2023 at 18:29:54 UTC+1, Lorem Ipsum wrote:
> > > On Monday, May 15, 2023 at 5:45:22 AM UTC-4, Jurgen Pitaske wrote:
> > > > On Monday, 15 May 2023 at 08:18:10 UTC+1, Lorem Ipsum wrote:
> > > > > On Sunday, May 14, 2023 at 3:30:15 AM UTC-4, Jurgen Pitaske wrote:
> > > > > > It seems you memories are fading.
> > > > > > Have a look here for
> > > > > > WHAT HAPPENED AT TESTRA:
> > > > > > https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0/m/mvVy-GN7AwAJ
> > > > > >
> > > > > > But does it really matter?
> > > > > > John Hart is posting interesting information one generation later.
> > > > > >
> > > > > > You gave a monkeys about such a project for 30 years now. Did not share anything.
> > > > > > 10 000 times you woke up and decided
> > > > > > - I will not tell anybody about this project,
> > > > > > just concentate on concentrated agression and lies..
> > > > > >
> > > > > > I am looking forward to more interesting information from John,
> > > > > Then why are you talking to Hugh? Do you ever get anything useful from such discourse?
> > > > >
> > > > > I should ask myself why I try to talk to you about talking to Hugh. Most people know not to engage him. I don't know why I try to get through to you about this. I guess I have the same mental illness as you.
> > > > >
> > > > > --
> > > > >
> > > > > Rick C.
> > > > >
> > > > > - Get 1,000 miles of free Supercharging
> > > > > - Tesla referral code - https://ts.la/richard11209
> > > > I post when I feel like.
> > > Yes, exactly. You are posting very emotionally, spewing your bile across the group. I've tried to explain this to you before, but you can't comprehend that YOUR BILE is just as bad for Forth and the clf group, as HIS BILE. I've come to realize that in many ways, the two of you are cut from the same cloth. I should never bother to try to explain this to you. I have done so many times, but you shrug it off as you believe you are on a pure quest and can do no harm.
> > > > He has been agressive enough against me and MPE when I was working for them.
> > > > This is now for more than 10 years.
> > > He is a nut, posting crap on the Internet. It's hard to imagine that is of any real harm to you, in any way. Ignore him, and he goes away. 99% of us here manage to do that. Why can't you?
> > > > This Forth Killer will not stop until he dies.
> > > You can't kill something that is already dead.
> > > > But at least others should know, and not everybody should let him piss off everybody
> > > > and make people move away from here and from Forth.
> > > Wait, are you talking about Hugh, or yourself?
> > > > The WHAT HAPPENED AT TESTRA was one of the best posts I ever started.
> > > > More people read this than any other post I have seen here.
> > > > So they know now.
> > > >
> > > > Why you waste everybodies time with such a post of yours I do not understand.
> > > That is the funniest thing you have ever written. LOL
> > > > But there we are.
> > > > This had been discussed here many many times before.
> > > Yes, and you never learn. I'm sorry I bothered you. In the future, I'll try to refrain from providing you with a view into reality.
> > >
> > > --
> > >
> > > Rick C.
> > >
> > > + Get 1,000 miles of free Supercharging
> > > + Tesla referral code - https://ts.la/richard11209
> > How you try to sell your bullshit is just funny
> > - but as there is not much else here
> > - you will continue anyway.
> > Though every time you say you will not.
> > Very funny again.
> >
> > If Forth is dead for you - why are you here?
> > No Wife, no friends - but CLF ?
> Yes, I think of clf as my wife. I guess it is your mistress. Should I be jealous?
>
> You have to admit, you are good material for any stand up comedian. I think in all the times I've tried to explain to you how your vitriolic posts are just as bad as anyone else's, only one time did you give up the "battle" and not respond. I call it a "battle", because that is how you have refereed to it.
>
> Whatever, this is very thin entertainment. It's not entirely different from teasing the town fool. When others do it, it can be amusing, but it's not something I have much fun doing. Still, I'm waiting for a contract, so I do get bored.
>
> --
>
> Rick C.
>
> -- Get 1,000 miles of free Supercharging
> -- Tesla referral code - https://ts.la/richard11209

How you try to sell your bullshit is just funny
- but as there is not much else here
- you will continue anyway.
Though every time you say you will not.
Very funny again.

If Forth is dead for you - why are you here?
No Wife, no friends - but CLF ?

On 17/05/2023 3:30 pm, Jurgen Pitaske wrote:
>
> If Forth is dead for you - why are you here?
> No Wife, no friends - but CLF ?

It's as good a place as any to see the world in microcosm.

On Wednesday, 17 May 2023 at 09:16:09 UTC+1, dxforth wrote:
> On 17/05/2023 3:30 pm, Jurgen Pitaske wrote:
> >
> > If Forth is dead for you - why are you here?
> > No Wife, no friends - but CLF ?
> It's as good a place as any to see the world in microcosm.

It is just sad to see
that John tries to give a projet to the Forth community,
but too many posts are neither Forth related nor Project related.

On 17/05/2023 7:11 pm, Jurgen Pitaske wrote:
> On Wednesday, 17 May 2023 at 09:16:09 UTC+1, dxforth wrote:
>> On 17/05/2023 3:30 pm, Jurgen Pitaske wrote:
>>>
>>> If Forth is dead for you - why are you here?
>>> No Wife, no friends - but CLF ?
>> It's as good a place as any to see the world in microcosm.
>
> It is just sad to see
> that John tries to give a projet to the Forth community,
> but too many posts are neither Forth related nor Project related.

Why sadness when your posts are the most popular.

On 15/05/2023 7:45 pm, Jurgen Pitaske wrote:
>
> The WHAT HAPPENED AT TESTRA was one of the best posts I ever started.
> More people read this than any other post I have seen here.

On Wednesday, 17 May 2023 at 14:15:34 UTC+1, dxforth wrote:
> On 17/05/2023 7:11 pm, Jurgen Pitaske wrote:
> > On Wednesday, 17 May 2023 at 09:16:09 UTC+1, dxforth wrote:
> >> On 17/05/2023 3:30 pm, Jurgen Pitaske wrote:
> >>>
> >>> If Forth is dead for you - why are you here?
> >>> No Wife, no friends - but CLF ?
> >> It's as good a place as any to see the world in microcosm.
> >
> > It is just sad to see
> > that John tries to give a projet to the Forth community,
> > but too many posts are neither Forth related nor Project related.
> Why sadness when your posts are the most popular.
> On 15/05/2023 7:45 pm, Jurgen Pitaske wrote:
> >
> > The WHAT HAPPENED AT TESTRA was one of the best posts I ever started.
> > More people read this than any other post I have seen here.

If there are only a few who post here now,
this seemingly brings up the relative ( and probably undeserved) importance.

I rather want to see here information about Forth,
and what John Hart posts about.

On Wednesday, May 17, 2023 at 10:30:46 AM UTC-4, Jurgen Pitaske wrote:
> On Wednesday, 17 May 2023 at 14:15:34 UTC+1, dxforth wrote:
> > On 17/05/2023 7:11 pm, Jurgen Pitaske wrote:
> > > On Wednesday, 17 May 2023 at 09:16:09 UTC+1, dxforth wrote:
> > >> On 17/05/2023 3:30 pm, Jurgen Pitaske wrote:
> > >>>
> > >>> If Forth is dead for you - why are you here?
> > >>> No Wife, no friends - but CLF ?
> > >> It's as good a place as any to see the world in microcosm.
> > >
> > > It is just sad to see
> > > that John tries to give a projet to the Forth community,
> > > but too many posts are neither Forth related nor Project related.
> > Why sadness when your posts are the most popular.
> > On 15/05/2023 7:45 pm, Jurgen Pitaske wrote:
> > >
> > > The WHAT HAPPENED AT TESTRA was one of the best posts I ever started.
> > > More people read this than any other post I have seen here.
> If there are only a few who post here now,
> this seemingly brings up the relative ( and probably undeserved) importance.
>
> I rather want to see here information about Forth,
> and what John Hart posts about.

Maybe, just maybe, if you stop posting your personal complaints, someone else, like John Hart, can get some words in edgewise? The absolute worst thing you do is to reply to the one who shall not be named. That not only adds your garbage complaints, it means he will reply to you, further polluting the waters.

Why are you unable to see that you are a bigger problem in this regard than anyone else in this group?

Since my last post in this thread, you have posted three times, none of which are on topic for the thread! Stop complaining about others, and take responsibility for your own posts!!!

--

Rick C.

-+ Get 1,000 miles of free Supercharging
-+ Tesla referral code - https://ts.la/richard11209

On Sunday, May 14, 2023 at 12:30:15 AM UTC-7, Jurgen Pitaske wrote:
> On Saturday, 13 May 2023 at 21:30:55 UTC+1, Hugh Aguilar wrote:
> > On Wednesday, May 10, 2023 at 4:51:59 PM UTC-7, John Hart wrote:
> > > Lower case is used for Locals.
> > > { a 2b - c 2d - e f -1, 0 }
> > > a, 32b input
> > > 2b, 64b input (double)
> > > c, 32b temporary
> > > 2d, 64b temporary
> > > e, f, outputs
> > > -1, output available flag
> > > 0, no output flag
> > >
> > > 44 -> c, store 44 in c
> > > AT a, pointer to first local
> > >
> > > Comments?
> > You seem to be trying to implement local variables with data-types.
<clip>
Convention isn't dependent on Implimentation.
The question: Is a leading number (2) a good way to signify the local is a double?
The Code gets ugly using singles for doubles and that's the convention we established.

Global Variable Conventions for FPGA4th
VARIABLE AA \ single (32b)
SVARIABLE AS \ single & goes into VAR_SET
2VARIABLE BB \ double (64b)
S2VARIABLE BS \ double & goes into 2VAR_SET
0 ITEM X:X \ single
0 SITEM X:S \ single & goes into VAR_SET
0 2ITEM Y:Y \ double
0 S2ITEM Y:S \ double & goes into 2VAR_SET

Simulation variables, SIMLDF vocabulary, all NODES go into NODE_SET
CLOCK OSC \ creates %%OSC, a simulation clock
NODE SNA \ creates %SNA, an asynchronous 1bit vector (input & output state)
NODE SNS .CLK OSC \ creates %SNS, a synchronous 1bit vector
m l NODES BNA \ creates %BNA an asynchronous bus vector, (m=most, l=least significant bit)
m l NODES BNS .CLK OSC \ creates %BNS, a synchronous bus vector

nn >>I %SNS \ stores nn in the input state
nn >>O %SNS \ stores nn in the output state
nn >>IO %SNS \ stores nn in both states

%%OSC UPDATE-OUTPUTS \ copies inputs to outputs in nodes using the OSC clock

jrh

Reality is an information process, set in motion and sustained by God for a purpose.

On Monday, May 22, 2023 at 12:53:26 PM UTC-7, John Hart wrote:
> > On Saturday, 13 May 2023 at 21:30:55 UTC+1, Hugh Aguilar wrote:
> > > You seem to be trying to implement local variables with data-types.
> <clip>
> Convention isn't dependent on Implimentation.
> The question: Is a leading number (2) a good way to signify the local is a double?
> The Code gets ugly using singles for doubles and that's the convention we established.

Maintenance programmers live in a fantasy world in which programs are full of
"cruft," which they claim is dead code that was never used or was used in the past
but became obsolete yet was left in the software. The maintenance programmer's
greatest thrill is to delete cruft. The maintenance programmer will puff up his hollow
chest and brag: "I deleted X bytes of cruft from the software, and the software still
does what it is supposed to do, so I have simplified the program!"
The truth is that maintenance programmers can't program, so instead they delete
code that they claim is "cruft" but which is just code that they don't understand.

Most likely, the reason why John Hart lost my local-variable code is that some
super-duper little maintenance programmer determined it to be cruft and deleted it.
This was not just X bytes of code, but tens of kilobytes of code!
As I said, this code wasn't used in the motion-control program but was written for
use in the C-generated code, but the C compiler never got written. John Hart and
Tom Hart have both said that getting the motion-control program working on the
MiniForth was the primary goal, because that was where the money was, Most likely
John Hart and Tom Hart praised the maintenance programmer for deleting this
cruft as told him that this proved that he was 10* better programmer than I was.
When I visited, Tom Hart told me that the parade of maintenance programmers at
Testra had each made 2 or 3 times my wage. He considered them to be 2 or 3 times
better programmers than I was. They were super-duper cruft deleters, although
they never succeeded in figuring out how MFX works so they never wrote MFX code.

Tom Hart was always spouting pseudo-intellectual quasi-religious drivel in his
thirty-two ounce discourses. This is typical:

> Reality is an information process, set in motion and sustained by God for a purpose.

Now we find that Albert van der Horst is John Hart's #2 greatest fan
(Juergen Pintaske is #1 and will always be #1).

On Friday, April 28, 2023 at 3:14:56 AM UTC-7, none albert wrote:
> In article <474678ef-ab80-411a...@googlegroups.com>,
> Hugh Aguilar <hughag...@gmail.com> wrote:
> <SNIP>
> >Nobody should hire Testra because Tom Hart and John Hart are liars.
> Are that the Hart's you have worked for? The Hart's that keep a company
> running for decennia while you were plumbing are tax-driving?
>
> Groetjes Albert
> --
> Don't praise the day before the evening. One swallow doesn't make spring.
> You must not say "hey" before you have crossed the bridge. Don't sell the
> hide of the bear until you shot it. Better one bird in the hand than ten in
> the air. First gain is a cat spinning. - the Wise from Antrim -

What the hell does any of this pseudo-intellectual quasi-religious drivel mean?
"First gain is a cat spinning." WTF??? Put down your crack pipe, Albert! STFU!

Albert van der Horst is the same idiot who posted nonsense code and claimed
that it did a continued fraction calculation. He should work for Testra! LOL

On Tuesday, July 3, 2018 at 2:14:22 AM UTC-7, Albert van der Horst wrote:
> In article <0ff9666d-e22e-4370...@googlegroups.com>,
> <hughag...@gmail.com> wrote:
> >On Monday, July 2, 2018 at 3:54:28 AM UTC-7, Albert van der Horst wrote:
> >>
> >> \ You only need D- and D<> >> : .cf2 BEGIN 100000 0 DO 2OVER D- 2DUP 0. D<= IF I . LEAVE THEN
> >> LOOP 2DUP OR WHILE 2OVER D+
> >> .S KEY DROP \ Can leave this out
> >> 2SWAP REPEAT ;
>
> Make that correct by
> 2SWAP REPEAT 1 . ;
>
> >> "
> >>
> >> 3.141592653589793238
> >> 1.000000000000000000
> >> 2DUP D. 2OVER D. KEY DROP .cf2
> >
> >You don't know what continued fractions are
>
> Said the cab-driver to the mathematician
>
> > --- your code is nonsense ---
> It gives the same results as your code, except for the correction
> I gave.
>
> > you posted this as a loyalty demonstration to Elizabeth Rather.
> I must say, I feel a connection with ER, like we are in the
> same camp or something.

<I feel better now that you attacked me>

In article <c5d67d1d-266c-4fcc-ae36-b82b1e247555n@googlegroups.com>,
Hugh Aguilar <hughaguilar96@gmail.com> wrote:
>Maintenance programmers live in a fantasy world in which programs are full of
>"cruft," which they claim is dead code that was never used or was used
>in the past
>but became obsolete yet was left in the software. The maintenance programmer's
>greatest thrill is to delete cruft. The maintenance programmer will puff
>up his hollow
>chest and brag: "I deleted X bytes of cruft from the software, and the
>software still
>does what it is supposed to do, so I have simplified the program!"
>The truth is that maintenance programmers can't program, so instead they delete
>code that they claim is "cruft" but which is just code that they don't
>understand.

The truth of the matter is that it is ten times the effort to diligently
remove code that is not needed than to write it in the first place.
I must be more clever analysing code to conclude that it is not needed,
compared to the ones that adds it just in case it is needed.
I came across code that could never work and tried to add test cases.
Then the truth comes out: it was never used.

>
>Tom Hart was always spouting pseudo-intellectual quasi-religious drivel in his
>thirty-two ounce discourses. This is typical:
>
>> Reality is an information process, set in motion and sustained by God
>for a purpose.

I don't care for (one of the zillion) gods, but at least it is an
interesting perspective.

>
>Now we find that Albert van der Horst is John Hart's #2 greatest fan
>(Juergen Pintaske is #1 and will always be #1).

Thank you I enjoy the company of Hart, Rather and others.
<SNIP>
>
>What the hell does any of this pseudo-intellectual quasi-religious drivel mean?
>"First gain is a cat spinning." WTF??? Put down your crack pipe, Albert! STFU!
It is a translation of the Dutch saying "eerste gewin is kattegespin".
Much obliged if you supply a better translation.

>
>Albert van der Horst is the same idiot who posted nonsense code and claimed
>that it did a continued fraction calculation. He should work for Testra! LOL
>
>On Tuesday, July 3, 2018 at 2:14:22 AM UTC-7, Albert van der Horst wrote:
>> In article <0ff9666d-e22e-4370...@googlegroups.com>,
>> <hughag...@gmail.com> wrote:
>> >On Monday, July 2, 2018 at 3:54:28 AM UTC-7, Albert van der Horst wrote:
>> >>
>> >> \ You only need D- and D<=
>> >> : .cf2 BEGIN 100000 0 DO 2OVER D- 2DUP 0. D<= IF I . LEAVE THEN
>> >> LOOP 2DUP OR WHILE 2OVER D+
>> >> .S KEY DROP \ Can leave this out
>> >> 2SWAP REPEAT ;
>>
>> Make that correct by
>> 2SWAP REPEAT 1 . ;
>>
>> >> "
>> >>
>> >> 3.141592653589793238
>> >> 1.000000000000000000
>> >> 2DUP D. 2OVER D. KEY DROP .cf2
>> >
>> >You don't know what continued fractions are
>>
>> Said the cab-driver to the mathematician
>>
>> > --- your code is nonsense ---
<SNIP>

I leaves this in because it is interesting code.
It works and after all those years Aguilar has never tried
it to see that it works.

Groetjes Albert
--
Don't praise the day before the evening. One swallow doesn't make spring.
You must not say "hey" before you have crossed the bridge. Don't sell the
hide of the bear until you shot it. Better one bird in the hand than ten in
the air. First gain is a cat spinning. - the Wise from Antrim -

On Wednesday, 24 May 2023 at 09:54:49 UTC+1, none albert wrote:
> <I feel better now that you attacked me>
>

It is a translation of the Dutch saying "eerste gewin is kattegespin".
Much obliged if you supply a better translation.

"The first victory is the cat's purr"

In article <7d843197-90da-4d0c-9390-db929c6b4267n@googlegroups.com>,
Jurgen Pitaske <jpitaske@gmail.com> wrote:
>On Wednesday, 24 May 2023 at 09:54:49 UTC+1, none albert wrote:
>> <I feel better now that you attacked me>
>>
>
>It is a translation of the Dutch saying "eerste gewin is kattegespin".
>Much obliged if you supply a better translation.
>
>"The first victory is the cat's purr"

The Dutch saying is more about you going to the market and sell
a bundle in the first hour. "victory" doesn't seem the right word.

Groetjes Albert
--
Don't praise the day before the evening. One swallow doesn't make spring.
You must not say "hey" before you have crossed the bridge. Don't sell the
hide of the bear until you shot it. Better one bird in the hand than ten in
the air. First gain is a cat spinning. - the Wise from Antrim -

<clip all not having to do with the question:>

Is a leading number (2) a good way to signify the local is a double?

Global Variable Conventions for FPGA4th ( revised )

VARIABLE AA \ single (32b)
SVARIABLE AS \ single & goes into VAR_SET
2VARIABLE BB \ double (64b)
S2VARIABLE BS \ double & goes into 2VAR_SET
0 ITEM X:X \ single
0 SITEM X:S \ single & goes into VAR_SET
0 2ITEM Y:Y \ double
0 S2ITEM Y:S \ double & goes into 2VAR_SET

Simulation variables, SIMLDF vocabulary, all NODES go into NODE_SET

CLOCK OSC \ creates %%OSC, a simulation clock
NODE SNA \ creates %SNA, an asynchronous 1bit vector (input & output state)
NODE SNS .CLK OSC \ creates %SNS, a synchronous 1bit vector
m l NODES BNA \ creates %BNA an asynchronous bus vector, (m=most, l=least significant bit)
m l NODES BNS .CLK OSC \ creates %BNS, a synchronous bus vector

%SNA ( -- n ) \ returns the input state
O>> %SNA ( -- n ) \ returns the output state

nn >>I %SNS \ stores nn in the input state
nn >>O %SNS \ stores nn in the output state
nn >>IO %SNS \ stores nn in both states

%%OSC UPDATE-OUTPUTS \ copies inputs to outputs in nodes using the OSC clock

jrh

Reality is an information process, set in motion and sustained by God for a purpose.

ALL SHALL BE WELL
And from the time the vision was shown, I desired often to know
what our Lord’s meaning was. Fifteen years and more afterward I
was answered in my spiritual understanding, thus:
Would you know your Lord’s meaning in this vision?
Know it well, love is his meaning.
Who showed it to you? Love.
What did he show you? Love.
Why did he show it? For love.
Keep yourself therein, and you shall know and understand more
in the same but you shall never know nor understand any other
thing, forever.
Thus I was taught that love was our Lord’s meaning. And I saw
quite clearly in this and in all, that before God made us, he
loved us, which love was never slaked, nor ever shall be. And
in this love he has done all his work and in this love he has
made all things profitable to us. And in his love our life is
everlasting. In our creation, we have beginning, but the love
wherein he made us was in him with no beginning. And all this
shall be seen in God without end.

Dame Julian, 1373, first woman author. (English)