[Aldor-l] better don't type "hello" into that REPL!

[Alex Goldman]

On 6/12/05, Ralf Hemmecke <ralf at hemmecke.de> wrote:
> I confirm the segfault.
> 
> But it works without
>    #int history on
> though. In fact, I remember having some problems with the history
> feature before..
> For me it is more convenient to open
>    aldor -gloop
> in an emacs shell. So one has nicer command line editing features.

Having no `#int history on` just delays the inevitable. I can rarely
make REPL accept more than one or two dozen commands before
segfaulting.

I can make it segfault without typing any commands at all. Just hit
Ctrl-C at the prompt:

Is anyone using Aldor for anything at all?! If the interpreter
segfaults so easily, I don't want to imagine what the compiler (a
usually more complicated piece of software) must be like. Do you have
any faith in the code it produces?

$ aldor -gloop
     AA  L      DDDD      OOO    RRRR
    A A  L      D   D    O   O   R   R
   A  A  L      D    D  O     O  R   R
  AAAAA  L      D    D  O     O  RRRR
 A    A  L      D   D    O   O   R  R
A     A  LLLLL  DDDD      OOO    R   R

(c) Numerical Algorithms Group Ltd 1995-2001
Release: Aldor(C) version 1.0.2 for LINUX(glibc2.3) 
Type "#int help" for more details.
%1 >> Use '#quit' to quit Axiomxl.
Program fault (segmentation violation).#1 (Error) Program fault
(segmentation violation).