#1613 read_list(file_search()) empty %o:s


Maxima version: 5.17.0
Maxima build date: 19:8 12/4/2008
host type: i686-pc-mingw32
lisp-implementation-type: GNU Common Lisp (GCL)
lisp-implementation-version: GCL 2.6.8


results in ca 35(!) empty %o:s before it ends with a correct %o. This happens bot in wx and xMaxima.


  • Robert Dodier

    Robert Dodier - 2009-03-07

    Fixed (I hope) by r1.53 src/mload.lisp.
    Can someone with a Windows build environment please try it.

  • Dieter Kaiser

    Dieter Kaiser - 2010-07-05
    • status: open --> pending
  • Dieter Kaiser

    Dieter Kaiser - 2010-07-05

    I am not sure what is expected for this bug report. But I get the same message (without 35 empty lines) for Linux with SBCL and Windows with GCL. This is the result I get for Linux:

    (%i17) load(numericalio);L:read_list(file_search("datafil.txt"));
    numericalio: expected a string, instead found a ?null
    -- an error. To debug this try: debugmode(true);

    And this is the answer with Windows:

    (%i1) build_info();

    Maxima version: 5.20.1
    Maxima build date: 21:25 12/14/2009
    Host type: i686-pc-mingw32
    Lisp implementation type: GNU Common Lisp (GCL)
    Lisp implementation version: GCL 2.6.8

    (%i2) load(numericalio);L:read_list(file_search("datafil.txt"));
    d:/Programme/Maxima-5.20.1/share/maxima/5.20.1/share/contrib/numericalio\ /numericalio.mac
    numericalio: expected a string, instead found a ?symbol
    -- an error. To debug this try: debugmode(true);

    I think this bug report can be closed.
    Setting the status to pending and the resolution to fixed.

    Dieter Kaiser

  • SourceForge Robot

    • status: pending --> closed
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks