1:02:26kagevfyeah, I'm not following at all how / why you would use parenscript on the server other than to generate JS as part of the output of a page so it can be used / run on the frontend
1:06:26fiddlerwoaroofYou could always use node to run the generated javascript
1:07:58fiddlerwoaroofBut, I think "normally" you'd either compile to js files and serve them statically, or you'd compile to JS and serve it up with something like hunchentoot
1:11:19kagevfright ... that's what I've been doing ... the latter 2
1:11:42kagevfwell, actually just the latter 1 ... serving from hunchentoot
1:42:50Josh_2Currently I am representing lisp objects as javascript in my JS source code so that they can be referenced by other bits of JS code, no runtime overhead doing object lookups in js etc. Thanks jasom
8:04:11shka_i am getting the following warning from the quicklisp
8:04:19shka_contains definition for system "cl-ppcre-test". Please only define "cl-ppcre" and secondary systems with a name starting with "cl-ppcre/" (e.g. "cl-ppcre/test") in that file
8:05:16shka_can I please have an example of the properly defined tests subsystem?
8:48:12kagevfI get that warning too when I asdf:load-system something that uses that library
8:58:10splittistThat's an asdf warning. At some point it became fussy about, as it says, defsystems in the same file. So you would define (defsystem #:trivial-example (...)) and (defsystem #:trivial-example/tests (...)) But perhaps you meant something else.