Why LispOS?

[Rodrigo Ventura]

>>>>> "Christopher" == "Christopher J Vogt" <vogt@computer.org> writes:


    Christopher> A side affect of all this is that you virtually never have a crash.  No
    Christopher> system freeze, no blue screen of death, no core dump.  Most people ran
    Christopher> their Lispm until it ran out of virtual memory space, which in my case was
    Christopher> between once a week and once a month.  With todays gigabyte disks, I could
    Christopher> run for months without booting.

        Hum, is that really needed? You can run UNIX for years without
a reboot. I assume our LispOS will have that for granted, and event
not require reboot, but just a (gc).

    Christopher> Ever use a program and wonder how they coded it?  On a lispm you could just
    Christopher> "break" the program and poke around.  If it was system software, the
    Christopher> sources were included and you could m-. (edit definition) from the debugger
    Christopher> and be in the editor looking at the source code.

    Christopher> The System Constrcution Tool (SCT) was like defsystem on steroids.  I still
    Christopher> miss the patching facility.  m-x Add Patch and friends (Add Changed
    Christopher> Definitions etc.).

        That's a great feature. Can it be said that it reaches the
level of changing code on-the-fly, or even build a program while
running/debuging it. It could speed-up enormously development speed.

        Regards,

-- 
--

*** Rodrigo Martins de Matos Ventura, alias <Yoda>
***  yoda@isr.ist.utl.pt, http://www.isr.ist.utl.pt/~yoda
***   Instituto de Sistemas e Robotica, Polo de Lisboa
***    Instituto Superior Tecnico, Lisboa, Portugal
***     PGP Public Key available on my homepage
*** Key fingerprint = 0C 0A 25 58 46 CF 14 99  CF 9C AF 9E 10 02 BB 2A