Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!bu.edu!att!pacbell.com!ucsd!ucbvax!BRFAPESP.BITNET!UNBCIC
From: UNBCIC@BRFAPESP.BITNET
Newsgroups: comp.lang.forth
Subject: To stand-alone or not to stand-alone
Message-ID: <9101050107.AA00252@ucbvax.Berkeley.EDU>
Date: 4 Jan 91 18:51:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: UNBCIC%BRFAPESP.BITNET@SCFVM.GSFC.NASA.GOV
Organization: The Internet
Lines: 29

* Replying to myself

>>> Standalone applications... There is some confusion here... The most commom
>>> application in Forth *IS* Standalone, i.e., you turn on your computer, load
>>> Forth, load the application, and use it...

>>       This is almost EXACT definition of appplication that is NOT
>> stand-alone i.e. it can't be executed without some kind of intermediary ;-)
>                                                             ^^^^^^^^^^^^

> And what is the intermediary (in this case)? Forth? I agree with your
> definition of what is not stand-alone, but I can't see where my definition
> match with yours...

> Maybe the problem is with the "load". In this case, "load" can mean "load from
> ROM to RAM", "load, at BOOT, from drive", "just initialize it"...

Is the intermediary that you specified the user? I think the user is always
present you some way (turning on the machine?)... You can even be right (and I
wrong), but when I want to visualize a stand-alone application, I think in a
MUMPS system.

>>>                              (8-DCS)
>>            Zarko Berberski           EBERBERS@YUBGEF51.bitnet
>                              (8-DCS)

                              (8-DCS)
Daniel C. Sobral
UNBCIC@BRFAPESP.BITNET