guix-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

54/67: gnu: Add parenscript.


From: Pierre Neidhardt
Subject: 54/67: gnu: Add parenscript.
Date: Wed, 17 Oct 2018 04:20:20 -0400 (EDT)

ambrevar pushed a commit to branch wip-next-browser2
in repository guix.

commit 684687bfcf2ef9f0f283f425bf788af56791487c
Author: Pierre Neidhardt <address@hidden>
Date:   Fri Oct 5 16:14:30 2018 +0200

    gnu: Add parenscript.
    
    * gnu/packages/lisp.scm (cl-parenscript, ecl-parenscript, 
sbcl-parenscript): New variables.
---
 gnu/packages/lisp.scm | 60 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 60 insertions(+)

diff --git a/gnu/packages/lisp.scm b/gnu/packages/lisp.scm
index a045d79..ebe1968 100644
--- a/gnu/packages/lisp.scm
+++ b/gnu/packages/lisp.scm
@@ -3069,3 +3069,63 @@ package.")
        "The @command{cl-sqlite} package is an interface to the SQLite embedded
 relational database engine.")
       (license license:public-domain))))
+
+(define-public sbcl-parenscript
+  (let ((commit "061d8e286c81c3f45c84fb2b11ee7d83f590a8f8"))
+    (package
+      (name "sbcl-parenscript")
+      (version (git-version "2.6" "1" commit))
+      (source
+       (origin
+         (method git-fetch)
+         (uri (git-reference
+               (url "https://gitlab.common-lisp.net/parenscript/parenscript";)
+               (commit commit)))
+         (file-name (git-file-name "parenscript" version))
+         (sha256
+          (base32
+           "1kbhgsjbikc73m5cwdp4d4fdafyqcr1b7b630qjrziql0nh6mi3k"))))
+      (build-system asdf-build-system/sbcl)
+      (inputs
+       `(("cl-ppcre" ,sbcl-cl-ppcre)
+         ("anaphora" ,sbcl-anaphora)
+         ("named-readtables" ,sbcl-named-readtables)))
+      (home-page "https://common-lisp.net/project/parenscript/";)
+      (synopsis "Translator from a subset of Common Lisp to JavaScript")
+      (description
+       "Parenscript is a translator from an extended subset of Common Lisp to
+JavaScript.  Parenscript code can run almost identically on both the
+browser (as JavaScript) and server (as Common Lisp).
+
+Parenscript code is treated the same way as Common Lisp code, making the full
+power of Lisp macros available for JavaScript.  This provides a web
+development environment that is unmatched in its ability to reduce code
+duplication and provide advanced meta-programming facilities to web
+developers.
+
+At the same time, Parenscript is different from almost all other \"language
+X\" to JavaScript translators in that it imposes almost no overhead:
+
address@hidden
address@hidden No run-time dependencies: Any piece of Parenscript code is 
runnable
+as-is. There are no JavaScript files to include.
address@hidden Native types: Parenscript works entirely with native JavaScript 
data
+types. There are no new types introduced, and object prototypes are not
+touched.
address@hidden Native calling convention: Any JavaScript code can be called 
without the
+need for bindings. Likewise, Parenscript can be used to make efficient,
+self-contained JavaScript libraries.
address@hidden Readable code: Parenscript generates concise, formatted, 
idiomatic
+JavaScript code. Identifier names are preserved. This enables seamless
+debugging in tools like Firebug.
address@hidden Efficiency: Parenscript introduces minimal overhead for advanced 
Common
+Lisp features. The generated code is almost as fast as hand-written
+JavaScript.
address@hidden itemize\n")
+      (license license:bsd-3))))
+
+(define-public cl-parenscript
+  (sbcl-package->cl-source-package sbcl-parenscript))
+
+(define-public ecl-parenscript
+  (sbcl-package->ecl-package sbcl-parenscript))



reply via email to

[Prev in Thread] Current Thread [Next in Thread]