- 21 Oct, 2018 1 commit
-
-
Vladimir Sedach authored
-
- 16 Oct, 2018 1 commit
-
-
Vladimir Sedach authored
-
- 15 Oct, 2018 3 commits
-
-
Vladimir Sedach authored
-
Vladimir Sedach authored
-
Vladimir Sedach authored
-
- 13 Oct, 2018 1 commit
-
-
Vladimir Sedach authored
-
- 12 Oct, 2018 1 commit
-
-
Vladimir Sedach authored
-
- 11 Oct, 2018 1 commit
-
-
Vladimir Sedach authored
-
- 10 Oct, 2018 2 commits
-
-
Vladimir Sedach authored
-
Vladimir Sedach authored
-
- 07 Oct, 2018 6 commits
-
-
Vladimir Sedach authored
-
Vladimir Sedach authored
-
Vladimir Sedach authored
-
Vladimir Sedach authored
-
Vladimir Sedach authored
-
Vladimir Sedach authored
-
- 02 Oct, 2018 1 commit
-
-
Vladimir Sedach authored
-
- 07 Jul, 2018 1 commit
-
-
Vladimir Sedach authored
-
- 09 Jun, 2015 1 commit
-
-
Boris Smilga authored
Additions to 116f9ca9, to not replace Φ() with Φ.call(this) unless Φ refers to this. Also, fixed / added tests.
-
- 03 Feb, 2015 1 commit
-
-
Boris Smilga authored
-
- 25 Dec, 2014 1 commit
-
-
Boris Smilga authored
1. Named function bodies in Common Lisp may contain multiple DECLARE forms before or after the docstring (or even before *and* after). This feature is important for meta-programming by macros, and so PS should also support it. 2. Declarations should be allowed in PS forms whose Lisp namesakes allow them, to wit: in the macros WITH-SLOTS, MULTIPLE-VALUE-BIND, DO*, DO, DOTIMES, DOLIST, DESTRUCTURING-BIND, LET*, DEFUN, DEFSETF, and in the special forms LET, FLET, LABELS (letting out DEFMACRO, MACROLET, SYMBOL-MACROLET who are not translated to JavaScript). Before the present commit, most of them didn't handle declarations correctly. 3. Individual DECLARE forms should be allowed to contain multiple declaration specifiers, in particular, multiple SPECIAL specifiers. WITH-DECLARATION-EFFECTS used to ignore SPECIALs after the first one. 4. This commit also introduces LOCALLY as PS form because it simplifies the implementation of stuff from (2).
-
- 18 Dec, 2014 1 commit
-
-
Boris Smilga authored
-
- 15 Dec, 2014 1 commit
-
-
Boris Smilga authored
Getters and setter are defined in ECMAScript 5.1 sec. 11.1.5. A getter would be specified in a (CREATE ...) form as a name-value pair of the form (GET <NAME>) <EXPR>, where <NAME> is a symbol naming the object slot, and <EXPR> is the body of the getter. A setter would be specified as a name-value pair of the form (SET <NAME> <NEW-PARAM>) <EXPR>, where <NAME> is a symbol naming the object slot, <NEW-PARAM> is a symbol naming the setter's formal parameter for the assignment value, and <EXPR> is the body of the setter.
-
- 23 Feb, 2014 1 commit
-
-
Max Rottenkolber authored
-
- 14 Mar, 2013 2 commits
-
-
Daniel Gackle authored
-
Daniel Gackle authored
warning in CCL.)
-
- 02 Mar, 2013 1 commit
-
-
Daniel Gackle authored
-
- 29 Nov, 2012 3 commits
-
-
Vladimir Sedach authored
Fixed output test trig-bind1 to be consistent between Lisps that know that (floor 3.14) is a constant and those that don't
-
Vladimir Sedach authored
-
Boris Smilga authored
-
- 24 Nov, 2012 2 commits
-
-
Vladimir Sedach authored
Simplified output of APPLY for code like (apply (@ an-object foo) nil) where the object is a simple symbol
-
Boris Smilga authored
-
- 08 Oct, 2012 1 commit
-
-
Vladimir Sedach authored
-
- 15 Sep, 2012 1 commit
-
-
Vladimir Sedach authored
Fixed problem with loop-return-arg and loop bodies getting double compiled by getting rid of loop-return-arg. Thanks to Daniel Gackle for the bug report.
-
- 13 Sep, 2012 1 commit
-
-
Vladimir Sedach authored
Removed the pass-through capability from the new global variable-based multiple value return system and prettied up associated code generation.
-
- 04 Sep, 2012 1 commit
-
-
Vladimir Sedach authored
Clarified the behavior of CASE when it comes to symbols and fixed some other bugs in CASE and SWITCH forms. Thanks to Boris Smilga for the bug report.
-
- 28 Aug, 2012 2 commits
-
-
Daniel Gackle authored
-
Daniel Gackle authored
loops (basically the equivalent of CL's "BEING THE HASH KEYS OF"). Because JS for-in loops can't be simulated with WHILE, this required changing how LOOP generates code - with these additional benefits: simpler implementation; smaller generated loops; all iteration vars now within the scope of the JS loop form, so that the LOOP macro now has consistent scoping behavior with hard-coded FOR, WHILE, etc. (notably with respect to whether to generate a new binding per iteration for variables captured by a closure). There is also the disadvantage that for some complex loops a temporary local variable must be used to track whether the loop is on its first iteration or not.
-
- 11 Aug, 2012 1 commit
-
-
Vladimir Sedach authored
-
- 10 Aug, 2012 1 commit
-
-
Vladimir Sedach authored
-