- parenscript-devel - mailman3.common-lisp.net

[parenscript-devel] with-slots inconsistence
by Canhua 28 Aug '11

28 Aug '11

hi, I find that (with-slots (a b) this (a)) compiles to a(), rather than this.a(), as I would expected. Which one is what you expected?

2 3

[parenscript-devel] question about WHO-PS-HTML syntax
by Canhua 26 Aug '11

26 Aug '11

hi, what's the parenscript WHO-PS-HTML syntax of this html snippet: <p>t0<span>t1</span></p> I tried (who-ps-html (:p "t0" (:span "t1"))), which evals to an error, saying function :span is not defined. Althrough I also found that CL-WHO accepts the following: (who:with-html-output-to-string (s) (:p "t0" (:span "t1"))) Thanks.

2 2

[parenscript-devel] Parenscript 2.3 compilation problem
by Erik Huelsmann 25 Aug '11

25 Aug '11

Hi, This week, Alessio Stalla and I are trying to get Parenscript to compile on ABCL. We're using Parenscript 2.3 as distributed with Quicklisp. Parenscript 2.2 worked fine, after fixing a potential readtables issue. However, Parenscript 2.3 fails compilation during the compilation of the (DEFINE-EXPRESSION-OPERATOR LET # ...) toplevel form. The problem is that it generates an expression (VAR X), which is then expanded to (DEFPARAMETER X). However, that's non-conforming because the initial value is required according to the CLHS. Looking at the definition of the VAR macro, I see the problem: (defmacro VAR (name &optional value docstring) `(defparameter ,name ,@(when value (list value)) ...)) can indeed lead to a (DEFPAMETER X) I haven't found out if/why this isn't a problem on Parenscript 2.2 or why Parenscript 2.3 would cleanly compile on SBCL, because - like ABCL - it rejects forms like that. If it is ABCL that's broken here, could you help us fix it? If not, could you fix parenscript to work on ABCL? I'm eager to learn about your analysis of the situation. If you need help on settin up ABCL, I'll gladly provide it. Bye, Erik

2 2

[parenscript-devel] operator precedence issue
by Anthony Fairchild 11 Aug '11

11 Aug '11

Hi, I think I found a bug in parenscript: CL-USER> (ps (/ a (* b c))) "a / b * c;" I believe it should return "a / (b * c);". Checking the mailing list archives I see there was a problem with this expression but it seems to have been fixed: CL-USER> (ps (- x (- a b))) "x - (a - b);" Thanks!

2 4

[parenscript-devel] Problems with "new"
by Mentus Sarovar 06 Aug '11

06 Aug '11

Hello i am new to parenscript. i am stuck with my attempt to create an instance of a new object. Why does: (parenscript:ps (new (*date))) translates to: "new(Date());" instead of: "new Date();" i tried various possiblities but simply could not get it. How does on do it properly? Thanks for help Matus

2 2

[parenscript-devel] Source maps (was: parenscript on parenscript?)
by Nick Fitzgerald 28 Jul '11

28 Jul '11

How much work would it be to integrate this in to PS? I don't have the time to make the patch myself, but I will help as much as I can in any other way. We have a reference implementation of the parsing and generating the source maps which is written in JS: https://github.com/mozilla/source-map https://github.com/mozilla/source-map/blob/master/test/test-source-map-gene… _Nick_ On Thu, Jul 28, 2011 at 1:19 PM, Daniel Gackle <danielgackle(a)gmail.com>wrote: > This is great to hear! It's a feature I have wanted for a long time. > > On Thu, Jul 28, 2011 at 12:50 PM, Nick Fitzgerald <fitzgen(a)gmail.com>wrote: > >> I've been meaning to drop a line here for a while, but this seems as >> opportune as any other time. I'm currently interning at Mozilla and my >> project should make targeting JS easier whether from PS or eventually from >> CL. It requires some buy-in on the side of the compiler, but I think it is >> worth it. >> >> https://wiki.mozilla.org/DevTools/Features/SourceMap >> >> _Nick_ >> >> >> >> >> On Wed, Jul 27, 2011 at 1:47 PM, Daniel Gackle <danielgackle(a)gmail.com>wrote: >> >>> < It would also be nice to have the full-featured JS environments (V8, >>> Rhino, SpiderMonkey) as another target for CL deployment. > >>> >>> I think this is going to become increasingly important as the JS >>> implementations improve. The recent release of Clojurescript is an >>> indicator. >>> >>> We've actually switched Skysheet to using PS server-side as well as >>> client-side so we can deploy to V8 on the server. There are three >>> reasons for this: >>> >>> 1) it eliminates the impedance mismatch between our CL code and our PS >>> code, which was a drag on development (example: JS's hash objects >>> don't have a very good counterpart in CL; neither CL hashtables nor >>> plists/alists are a great substitute); >>> >>> 2) we get better performance from V8 than we do from SBCL. (That's for >>> unoptimized CL. Optimized CL would do much better of course, but that >>> would worsen the impedance mismatch described above; >>> >>> 3) interoperability with JS gives some desired conveniences, like V8's >>> fast JSON support and Node.js for non-blocking i/o. >>> >>> A full CL-in-JS would open the door to an all-CL system rather than an >>> all-JS one. Either would be better than straddling the two. Would we >>> switch? Hard to say. >>> >>> >>> On Wed, Jul 27, 2011 at 1:56 PM, Vladimir Sedach <vsedach(a)gmail.com>wrote: >>> >>>> Currently Parenscript uses some things from Common Lisp that aren't in >>>> Parenscript. The three approaches to make PS self-hosting are: >>>> >>>> 1. Rewrite PS code in a DSL that can be compiled with Parenscript. For >>>> example, replace car/cdr/etc. with destructuring and templating macros >>>> that translate to car/cdr for CL and array access in JS. Then on the >>>> JS side you'd construct your code from arrays instead of conses. The >>>> only problematic thing is symbol representation. >>>> >>>> 2. Implement the missing CL features as a run-time library (add a cons >>>> prototype with car/cdr methods). >>>> >>>> 3. Make a Common Lisp implementation that runs in JavaScript. >>>> >>>> I think the last option is the most overall useful, and the most fun >>>> to do. Parenscript then would (along with an existing CL >>>> implementation) act as a "syslisp"/bootstrapping dialect and >>>> cross-compiler. Red Daly already has large parts of the needed CL >>>> runtime implemented in his PSOS project >>>> (https://github.com/gonzojive/paren-psos) >>>> >>>> How useful would Parenscript be in the browser? My guess is not very. >>>> After all, it will just be a macro pre-processor over JavaScript's >>>> eval, and anything you can do with that you're better off doing with >>>> closures. >>>> >>>> OTOH having a full Common Lisp on the browser (*with* a working ASDF) >>>> would be pretty sweet. It would also be nice to have the full-featured >>>> JS environments (V8, Rhino, SpiderMonkey) as another target for CL >>>> deployment. >>>> >>>> Vladimir >>>> >>>> On Wed, Jul 27, 2011 at 7:24 AM, Anton Vodonosov <avodonosov(a)yandex.ru> >>>> wrote: >>>> > Hello. >>>> > >>>> > I am new in parenscript and only glanced through the documentation on >>>> the project page. >>>> > >>>> > As I understand parenscript source is compiled to javascript using a >>>> CL implemented compiler. >>>> > >>>> > It's interesting, how difficult it is to have the same compiler >>>> implemented on javascript (i.e. on parenscript itself). >>>> > >>>> > As parenscript is a subset of CL, in theory it mitght be not >>>> difficult. >>>> > >>>> > The goal - is to have a browser only Lisp implementation, that can >>>> work without hunchentoot. To include parenscript >>>> > scripts onto browser directly, redefine functions interactively and so >>>> on. >>>> > >>>> > What do you think? >>>> > >>>> > Best regards, >>>> > - Anton >>>> > >>>> > _______________________________________________ >>>> > parenscript-devel mailing list >>>> > parenscript-devel(a)common-lisp.net >>>> > >>>> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel >>>> > >>>> >>>> _______________________________________________ >>>> parenscript-devel mailing list >>>> parenscript-devel(a)common-lisp.net >>>> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel >>>> >>> >>> >>> _______________________________________________ >>> parenscript-devel mailing list >>> parenscript-devel(a)common-lisp.net >>> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel >>> >>> >> >> _______________________________________________ >> parenscript-devel mailing list >> parenscript-devel(a)common-lisp.net >> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel >> >> > > _______________________________________________ > parenscript-devel mailing list > parenscript-devel(a)common-lisp.net > http://lists.common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel > >

1 0

[parenscript-devel] parenscript on parenscript?
by Anton Vodonosov 28 Jul '11

28 Jul '11

Hello. I am new in parenscript and only glanced through the documentation on the project page. As I understand parenscript source is compiled to javascript using a CL implemented compiler. It's interesting, how difficult it is to have the same compiler implemented on javascript (i.e. on parenscript itself). As parenscript is a subset of CL, in theory it mitght be not difficult. The goal - is to have a browser only Lisp implementation, that can work without hunchentoot. To include parenscript scripts onto browser directly, redefine functions interactively and so on. What do you think? Best regards, - Anton

5 5

Re: [parenscript-devel] Bug in translation of / operator
by Leslie P. Polzer 12 Jul '11

12 Jul '11

Patch attached. Please let me know if you would rather have another solution to this. Leslie -------- Original-Nachricht -------- > Datum: Tue, 28 Jun 2011 12:22:49 +0200 > Von: "Leslie P. Polzer" <leslie.polzer(a)gmx.net> > An: parenscript-devel(a)common-lisp.net > Betreff: [parenscript-devel] Bug in translation of / operator > Parenscript 2.3: > > ? (/ 2) > 1/2 > > ? (ps:ps (/ 2)) > "2;" > > ;; should be 1/2 > > Leslie > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > _______________________________________________ > parenscript-devel mailing list > parenscript-devel(a)common-lisp.net > http://lists.common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

2 1

[parenscript-devel] Bug in translation of / operator
by Leslie P. Polzer 28 Jun '11

28 Jun '11

Parenscript 2.3: ? (/ 2) 1/2 ? (ps:ps (/ 2)) "2;" ;; should be 1/2 Leslie -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

1 0

[parenscript-devel] Possible bug in Parenscript 2.3 (*ps-lisp-library*)
by TeMPOraL 19 Jun '11

19 Jun '11

Hi, I am working on CCL and I have migrated from Parenscript 2.2 to 2.3, and now I get warnings (pasted below) when including Parenscript runtime library (*ps-lisp-library*). Generated Javascript has bugs; in particular, 'member' function always returns false. WARNING: CL-USER> (parenscript:ps* parenscript:*ps-lisp-library*) ; Warning: Returning from unknown block nilBlock ; While executing: PARENSCRIPT::RETURN-EXP, in process repl-thread(9). ; Warning: Returning from unknown block nilBlock ; While executing: PARENSCRIPT::RETURN-EXP, in process repl-thread(9). ; Warning: Returning from unknown block nilBlock ; While executing: PARENSCRIPT::RETURN-EXP, in process repl-thread(9). ; Warning: Returning from unknown block nilBlock ; While executing: PARENSCRIPT::RETURN-EXP, in process repl-thread(9). ; Warning: Trying to (RETURN TRUE) from inside a loop with an implicit nil block (DO, DOLIST, DOTIMES, etc.). Parenscript doesn't support returning values this way from inside a loop yet! ; While executing: #<Anonymous Function #x9D6C98E>, in process repl-thread(9). ; Warning: Returning from unknown block nilBlock ; While executing: PARENSCRIPT::RETURN-EXP, in process repl-thread(9). ; Warning: Returning from unknown block nilBlock ; While executing: PARENSCRIPT::RETURN-EXP, in process repl-thread(9). ; Warning: Returning from unknown block nilBlock ; While executing: PARENSCRIPT::RETURN-EXP, in process repl-thread(9). Result: (...) /** Check if ITEM is a member of ARR. */ function member(item, arr) { for (var el = null, _js_idx176 = 0; _js_idx176 < arr.length; _js_idx176 += 1) { el = arr[_js_idx176]; if (el === item) { break; }; }; return false; }; (...) Regards, -- Jacek Złydach, http://temporal.pr0.pl/devblog TRC - Bringing you tomorrow's solutions yesterday.

2 3