Re: The strengths of FORTH

On Mar 28, 10:50 am, "dkel...@[EMAIL PROTECTED]
" <dkel...@[EMAIL PROTECTED]
>
wrote:
> Hi
>  One of the complaints I see often is the lack
> of type checking.
>  I can't recall when I had an error in my code
> related to incorrect use of type. Still, it is
> considered a major problem with Forth?
> Dwight

Is it a major problem? Of course not. It requires
reliance on at least one of a range of alternative
programming disciplines, and if someone is aware
of what the range of alternatives are, and doesn't
want to use one (or more) of them, they don't want
to program in Forth.

It was, originally, a language design decision that
if the programmer wanted to  add 6 to a letter and
then use that as a boolean, that was the programmer's
business and not the compiler's.

That entitlement was an assumption of current practice
when the Forth-94 source code standard was established,
so it is embedded in Forth-94.

If someone wants that to be the compiler's decision to
disallow that (sometimes unless you go through a process)
of asking nicely first), and want the other features of
Forth, and wants it to be as closed to Forth-94 as possible
within the constraints required for type-checking, then from
what I understand StrongForth does that.