API Reference


Parenscript library for compiling files and ASDF systems.


The Parenscript reader.  Used for reading Parenscript forms.

The only significant difference between this and the standard lisp reader is that package names are
script package names rather than Lisp package names.
No exported symbols.


ASDF extensions that help compile and use Parenscript systems.
  • Function COMPILE-SCRIPT-SYSTEM (system &rest rest)
  • Function COMPILE-SCRIPT-SYSTEM (system &key (pretty-print t) (output-spec :javascript) (output-to-stream t) (output-stream *standard-output*) output-to-files comp-env)
    Compiles a collection of parenscripts as described by an ASDF system into files or a specified output stream.


Library that compiles Parenscript files and systems.
  • Function READ-PARENSCRIPT-FORM (&optional (stream *standard-input*) eof-error-op eof-value recursivep)
    Reads a parenscript form from a stream. Use instead of READ so we can replace the reader with a parenscript reader, if necessary.
  • Function COMPILE-SCRIPT-FILE (source-file &key (output-spec :javascript) comp-env (pretty-print t) (output-stream *standard-output*))
    Compiles the given Parenscript source file and outputs the results to the given output stream.
  • Function COMPILE-SCRIPT-FILE-TO-STRING (source-file &rest rest)
    Compile SOURCE-FILE (a parenscript file) to a javascript string. (in-package ...) forms behave as expected and all other forms are evaluated according to the value of EVAL-FORMS-P. If the result of the evaluation is not nil then it's compiled with js:js* and written to the output.
  • Function COMPILE-SCRIPT-FILE-TO-JS-FILE (source-file &rest args &key destination-file &allow-other-keys)
    Compile SOURCE-FILE (a parenscript file) to a javascript file with compile-parenscript-file-to-string. When DESTINATION-FILE is omitted, then it will be named the same as SOURCE-FILE but with js extension.

Also exports