Print Page - [bug] (command-line nil) ?

Title: [bug] (command-line nil) ?
Post by: newdep on April 21, 2008, 03:23:08 AM

Hi Lutz,

newlisp 9.3.8

>(command-line nil)

results in a 100% cpu load under linux

Title:
Post by: Lutz on April 21, 2008, 07:42:04 AM

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.

Title:
Post by: newdep on April 21, 2008, 10:56:57 AM

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

newLISP Fan Club

Forum => newLISP in the real world => Topic started by: newdep on April 21, 2008, 03:23:08 AM