On 12/31/2010 03:17 AM, Robert Dodier wrote:
> On 12/30/10, andre maute<andre.maute at gmx.de> wrote:
>
>> P.S: was either of the two mechanisms documented somewhere?
> Well, file_type is documented in the reference manual,
> but the description is out of date.
Well I meant if load can only load
files with a specific extension
that should be documented at the place where
the documentation of load is.
Andre
Now it reads
------------(Maxima 5.22.1)------------
_
Function:_ *load*/(filename)/
Evaluates expressions in filename, thus bringing variables, functions,
and other objects into Maxima. The binding of any existing object is
clobbered by the binding recovered from filename. To find the file,
|load| calls |file_search| with |file_search_maxima| and
|file_search_lisp| as the search directories. If |load| succeeds, it
returns the name of the file. Otherwise |load|
prints an error message. |
load| works equally well for Lisp code and Maxima code. Files created by
|save|, |translate_file|, and |compile_file|, which create Lisp code,
and |stringout|, which creates Maxima code, can all be processed by
|load|. |load| calls |loadfile| to load Lisp files and |batchload|to
load Maxima files. |
load| does not recognize |:lisp| constructs in Maxima files, and while
processing filename, the global variables |_|, |__|, |%|, and |%th| have
whatever bindings they had when |load| was called.
See also |loadfile|, |batch|, |batchload|, and |demo|. |loadfile|
processes Lisp files; |batch|, |batchload|, and |demo| process Maxima files.
See |file_search| for more detail about the file search mechanism.
|load| evaluates its argument.
------------------------------------------------