Skip to content
  1. Mar 05, 2019
  2. Jul 07, 2018
  3. Oct 10, 2012
  4. Feb 03, 2011
  5. Jan 30, 2011
  6. Nov 22, 2010
  7. Nov 13, 2010
  8. Nov 04, 2010
  9. Aug 22, 2010
  10. Aug 14, 2010
  11. Apr 22, 2010
  12. Apr 18, 2010
  13. Dec 27, 2009
  14. Dec 25, 2009
  15. May 09, 2009
    • Vladimir Sedach's avatar
      Substantially modified the way Parenscript compilation and · 5a69278c
      Vladimir Sedach authored
      macro-expansion take place. This gives control of macroexpansion to
      special forms, and lets Parenscript do things like fake being a Lisp2
      (different function and variable namespaces), and overall makes
      Parenscript compilation look a lot more like CL compilation.
      5a69278c
  16. May 03, 2009
    • Vladimir Sedach's avatar
      Implemented LET and LET* by variable renaming, which provides the · 5ffb1eba
      Vladimir Sedach authored
      correct scoping semantics, and simplifies both the producing and the
      produced code.
      
      Removed the "." and "[]" name-mangling conventions from
      symbol-to-js-string. Any code that uses symbols such as "foo.bar[baz]"
      will now issue a warning, and needs to be rewritten to use standard
      Lisp accessors. This is needed for variable renaming to work, and is
      an extension of the patch that eliminated the ".method" method-calling
      convention.
      
      Thanks to Daniel Gackle and Dough Hoyte for opening my eyes to this
      technique, which was right in front of me all along.
      5ffb1eba
  17. Apr 13, 2009
  18. Apr 12, 2009
  19. Apr 06, 2009
  20. Jan 19, 2009
  21. Dec 30, 2008
  22. Dec 26, 2007
  23. Nov 15, 2007
  24. Nov 04, 2007
  25. Oct 29, 2007
  26. Oct 14, 2007
  27. Sep 23, 2007
  28. Aug 15, 2007
  29. Aug 12, 2007
  30. Aug 04, 2007
  31. Aug 01, 2007
  32. Jul 27, 2007
    • Red Daly's avatar
      ASDF interaction for Parenscript files · a9fce0a7
      Red Daly authored
      see the new paren-asdf.lisp and updated compilation-interface.lisp
      files for implementation details.  The function COMPILE-SCRIPT-SYSTEM
      compiles all the system's files and outputs them to a single stream.
      Currently it compiles each file separately; in the future we will
      probably need to compile the whole program and then translate it.
      a9fce0a7
  33. Jul 25, 2007
    • Red Daly's avatar
      usable package system · 171bbab3
      Red Daly authored
      The package system is now fairly usable.  package.lisp and
      builtin-packages.lisp now intelligently share symbols.  It is also
      possible to completely ignore any package system functionality.
      171bbab3
  34. Jul 24, 2007
  35. Jul 20, 2007
    • Red Daly's avatar
      renaming and refactoring · 9da682ca
      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).
      9da682ca
  36. Jul 03, 2007
  37. Jun 26, 2007
    • Red Daly's avatar
      js.lisp breakup · cc4f1551
      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
      cc4f1551