[bug] (command-line nil) ?

[newdep]

Hi Lutz,



newlisp 9.3.8



>(command-line nil)

results in a 100% cpu load under linux

[Lutz]

A program disabling the command line should never get there, but sit in a 'read-line' or other I/O statement waiting for input. If on the toplevel as last statement, it will basically hang in an empty loop. I inserted a sleep for this situation in tomorrows development release.



For a program using (command-line nil) the best would be to have an (exit) statement at the end of the file.

[newdep]

aaaaa i remember now, ive asked this befor... Sorry ;-)