#115 maxima-getenv returns "" instead of NIL

closed
nobody
5
2012-12-04
2002-08-26
Julian Stecklina
No

During startup the function maxima-getenv returns ""
instead of NIL for certain environment variables.
Happens with CLISP 2.28 and CMU CL 18d. This causes
trouble as CMU CL and CLISP try to load the current
directory (as file) when e.g.

(if maxima_int_lisp_preload
(load maxima_int_lisp_preload))

is evaluated (with maxima_int_lisp_preload="" and thus
true)

Maxima version: 5.9.0pre-cvs
Maxima build date: 23:20 8/26/2002
host type: i386-unknown-freebsd4.6.2
lisp-implementation-type: CMU Common Lisp
lisp-implementation-version: 18d

Discussion

  • Logged In: NO

    This seems to be a bug in some (particularly the one that
    comes with FreeBSD) implementations of sh (but it just as well
    might be a feature because I don't think POSIX says anything
    about declared but unbound variables). The easiest way to
    get rid of this is to fix the maxima start-up script by moving
    "export MAXIMA_INT_LISP_PRELOAD" and friends to the
    corresponding "if ... fi" blocks that check for presence of
    command-line switches (ll. 220-241 in the 5.9.0 tarball).

     
  • Robert Dodier
    Robert Dodier
    2006-06-26

    • summary: maxima-getenv returns "" instead of NIL --> maxima-getenv returns "" instead of NIL
    • labels: --> Installation
    • milestone: --> To_be_reviewed
     
  • Robert Dodier
    Robert Dodier
    2006-06-26

    Logged In: YES
    user_id=501686

    Marking this "to be reviewed". It seems plausible that the
    code involved has been revised (maybe to fix something else)
    since this report was filed.

     
  • Dieter Kaiser
    Dieter Kaiser
    2009-05-26

    The Maxima and the Lisp versions are out of date. The function maxima-getenv is used in init-cl.lisp. This file has been revised a lot in the last years. Setting the status to pending.

    Dieter Kaiser

     
  • Dieter Kaiser
    Dieter Kaiser
    2009-05-26

    • status: open --> pending
     
    • status: pending --> closed
     
  • 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).