- 24 Aug, 2007 2 commits
-
-
Vladimir Sedach authored
-
Vladimir Sedach authored
-
- 23 Aug, 2007 3 commits
-
-
Vladimir Sedach authored
-
Vladimir Sedach authored
-
Vladimir Sedach authored
-
- 15 Aug, 2007 2 commits
-
-
Vladimir Sedach authored
-
Vladimir Sedach authored
Now everything gets written to a stream.
-
- 12 Aug, 2007 2 commits
-
-
Vladimir Sedach authored
-
Vladimir Sedach authored
-
- 04 Aug, 2007 1 commit
-
-
Vladimir Sedach authored
-
- 03 Aug, 2007 2 commits
-
-
Red Daly authored
I also fixed some problems with nil serialization and decomposed the compile-parenscript-form function into a generic function with different behavior depending on the type of form.
-
Vladimir Sedach authored
Changed package system so that symbols in parenscript, javascript and parenscript-user are non-prefixed. Made symbols in unknown packages be treated as though they were in parenscript-user by default. Added a prefix string preference to PS packages. Removed all *enable-package-system* stuff.
-
- 01 Aug, 2007 2 commits
-
-
Vladimir Sedach authored
-
Red Daly authored
-
- 26 Jul, 2007 1 commit
-
-
Vladimir Sedach authored
(slot-value object slot) should now handle cases where object is an arbitrary expression correctly.
-
- 24 Jul, 2007 1 commit
-
-
Red Daly authored
-
- 20 Jul, 2007 1 commit
-
-
Red Daly authored
Changed the names of many functions and macros to get rid of the symbols with "js" in them--its not Javascript, it's Parenscript! Most of those symbols were renamed with "script" replacing "js". Also changed the main compilation interfaces to use the function COMPILE-SCRIPT and the macro SCRIPT from JS-COMPILE and JS respectively. Additionally, the first steps of the package system are included (with the addition of a the SCRIPT-PACKAGE and COMPILATION-ENVIRONMENT classes). These are integrated into the current compiler, though they probably break a few "traditional" serialization methods, specifically because macro and special form names are stored as symbols rather than strings and EQL comparisons are used rather than STRING-EQUAL comparisons of the strings. I have also split parser.lisp into parser.lisp and macrology.lisp. Parser.lisp contains mechanisms for parsing Parenscript given an input s-expression while macrology.lisp contains language definitions that make use of the parsing mechanisms. All tests now pass, though the documentation has gone slightly out of date with the symbol renaming. This will be fixed shortly. More tests and functionality need to be added to make the current Parenscript compatable with the older semantics (as dicussed, comparing macro/special form names based on their string values is the main thing).
-
- 26 Jun, 2007 1 commit
-
-
Red Daly authored
Broke the js.lisp file up into several three files: source-model.lisp, js-translation.lisp, and parser.lisp. source-model.lisp: class definitions that correspond to the Javascript AST. (defjsclass forms for the most part) js-translation.lisp: functions for converting AST objects to Javascript source code parser.lisp: macro definitions and the mechanisms for processing Parenscript forms into AST objects. See also: http://common-lisp.net/pipermail/parenscript-devel/2007-June/000035.html
-