darcs-hash:5d34d4643b3798b0336604c08a5777cbf2bc6f4f

darcs-hash:2710505a40f53bab1c83e7a69dc3f8de2239c912

darcs-hash:070cae4bee9efe1c4fd358e45537f2e29dbe295f

I have a minor patch that fixes the following incorrect (or at least
unexpected) behavior in ParenScript.

(js (- 1))  =>  "1;"
(js (incf x 5))   => an error
(js (decf x 5))   => an error

darcs-hash:cff90c9f9f195531ccf655b0c6f5bf449443b79e

darcs-hash:502a5a90ee3b292df4e484871f349052829a8eb0

darcs-hash:3acbbe4595cba8dbedd0085ff42854cc16135f31

(js:js (+ 42 '"FoooFFFOFOFooo")) => "42 + FoooFFFOFOFooo;"
IOW, quote inside a parenscript form means to simply print the quoted value as-is.
Among other things, this is useful for inserting literal javascript into parenscript.
I hope it will not break anything.

darcs-hash:7a3dbb342494cd4753a4ed648db85786ea27c6fb

darcs-hash:111c204152bbe19f3afafc3256ea3983aa75e0be

darcs-hash:079d5da4a340cf6ba2041420938dbd2a5e4c5bca

darcs-hash:0eab6196517ec9ea323e8af04fbb69ae368d02b2

darcs-hash:7d75a34ad3f5017aac2f4c2d1e49e732d4b68c58

darcs-hash:da55ae3daeeb910aadfecb87747074a45ffdb4e4

darcs-hash:6a1922588591c1aba3d1e2cf7516b133a3c4de4f

darcs-hash:28fe6540b5e1d71fff7c2e1ebc63f48a61760436

darcs-hash:f4219de1d487f0ec0492a3fe96739bc5903be275

darcs-hash:a13b0a4e14f4ef1a237b424aeb2f95c985c0bfcd

darcs-hash:e8cf344d5cdfd6b154daebf6257e90d7df8e4ec8

darcs-hash:e3acd5be1bef7fd9db2ef5bc05981fab0ca3f80e

darcs-hash:3a64461311d0cb420de9f48b1c73133abd72e36d

Previously the syntax of with was this:
  (with (object)
    body)

now it's:
  (with object
    body)

It was also broken when 'object' was an expression...

darcs-hash:8375b20a6aeae85c0a3c450452df520f50abd9c4

darcs-hash:135600cf6bec89b1d2daa1c755057ebcb6704198

darcs-hash:d4cfa444b185dbed71f49334d9a5a2cb4f6e7f17

darcs-hash:e067fca28938423ff77e12729f5988a07a09943a

darcs-hash:1e1b0eec011e289711c151cd3e63e82fe39bbff4

This is a first element of an parenscript library. The contents of
this file is to be compiled with parenscript and the result js included
in the host environment in one way or another.

darcs-hash:7faee100032549ddd1916d3cbd12fe281979e80f

darcs-hash:db25863e2848bd55e1e3e80677ff1db0e636ddaa

darcs-hash:9d07effb9c5c4639189919dae76ba7c86aaf4034

In the long run we should cut js.lisp into several files. One dealing with
the basic infrastructure like macro expansion, and the rest implementing
the compiler based on this infrastructure/utilities.

darcs-hash:1282de86846fb11c62dce7bcad6c5d3331f96c4b

darcs-hash:d2e9ac392966eea4370bb7b508edfaf3646d27ee

darcs-hash:b478f07f02960d8193d39cd28d425f3781c04549

For details see http://sourceforge.net/tracker/index.php?func=detail&aid=1516684&group_id=1355&atid=101355

darcs-hash:4c7f0e040152d52946bbbdee6418059095e289ef

darcs-hash:cf0bc884308d98487a601344b28ee1314baa3272

darcs-hash:f5a391d5de8fbfd0ec028496c4f02cf3a093e734

darcs-hash:72eca5cd28854044963f5453ac30dcbaca2aea3d

The problew is that compile-parenscript-file-to-string contains a call
to the macro js:js* this macro needs to be defined before we compile
the compile-parenscript-file-to-string function.

darcs-hash:0be874682be6010a22749e611be87ad15b4da8bb

darcs-hash:868b767aaccbb54c9f5e2b8fbdeffe1a97364571

darcs-hash:b63c6c28c6b798289f5f21f0ae4e5a3a53b93743

darcs-hash:d63a7da06998b4b73b9ae8e9f53c0791d96d0c01

darcs-hash:7189fb405eec9f517035b0ed4e4519ca98e5dada

darcs-hash:4defa1294b6ded04f3f2460bcc3aeeccdbf46fcf