Re: Portable Software

Hans-Peter Diettrich <>
Fri, 7 Apr 2023 15:35:32 +0200

          From comp.compilers

Related articles
[4 earlier articles]
Re: Portable Software (was: fledgling assembler programmer) (2023-03-28)
Re: Portable Software (Hans-Peter Diettrich) (2023-03-31)
Re: Portable Software (2023-04-02)
Re: Portable Software (Hans-Peter Diettrich) (2023-04-05)
Re: Portable Software (2023-04-05)
Re: Portable Software (Kaz Kylheku) (2023-04-06)
Re: Portable Software (Hans-Peter Diettrich) (2023-04-07)
Re: Portable Software (Thomas Koenig) (2023-04-08)
| List of all articles for this month |

From: Hans-Peter Diettrich <>
Newsgroups: comp.compilers
Date: Fri, 7 Apr 2023 15:35:32 +0200
Organization: Compilers Central
References: 23-03-001 23-03-017 23-03-022 23-03-029 23-03-032 23-03-042 23-04-005 23-04-006 23-04-007
Injection-Info:; posting-host=""; logging-data="88519"; mail-complaints-to=""
Keywords: design
Posted-Date: 07 Apr 2023 10:51:46 EDT
In-Reply-To: 23-04-007

On 4/5/23 6:30 PM, Anton Ertl wrote:
> Hans-Peter Diettrich <> writes:

> You mean: Write your program in Java, Python, Gforth, or the like?
> Sure, they deal with compatibility problems for you, but you may want
> to do things (or have performance) that they do not offer, or only
> offer through a C interface (and in the latter case you run into the
> C-level compatibility again).

Except the library also is portable ;-)

Else you end up with:
      Program runs only on systems with libraries X, Y, Z installed.

>> (G)FORTH IMO is a special case because it's (also) a development system.
>> Building (bootstrapping) a new FORTH system written in FORTH is quite
>> complicated, in contrast to languages with stand alone tools like
>> compiler, linker etc.
> Not really. Most self-respecting languages have their compiler(s)
> implemented in the language itself, resulting in having to bootstrap.

The FORTH compiler also is part of the current monolithic framework.
Replacing a WORD has immediate impact on the just running compiler and
everything else. A bug can make the current system crash immediately,
without diagnostics. Else the current WORDs can not be replaced
immediately, only after a full compilation and only by code that depends
on neither the old nor the new framrwork.

> AFAIK the problem Gforth has with Windows is not the bootstrapping;
> packaging and installation are different than for Unix.

Isn't that the same problem with every language?


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.