Hi everybody,
I just pushed a bunch of patches greatly improving Parenscript compilation performance, and adding the ability to print Parenscript output directly to a stream. I think it's time to make a release. Please check out the latest version from the git repository and see if everything works as expected. If there aren't any bug reports by Sept. 18, I am going to make a new release.
Thank you, Vladimir
I just ran our regression tests and am noticing one problem: some symbol macros aren't expanding. This seems like it might be the return of a bug I posted about before. I don't have time to post an example at the moment (I can do so later), but thought I should report the issue.
On Sun, Sep 13, 2009 at 4:23 PM, Vladimir Sedach vsedach@gmail.com wrote:
Hi everybody,
I just pushed a bunch of patches greatly improving Parenscript compilation performance, and adding the ability to print Parenscript output directly to a stream. I think it's time to make a release. Please check out the latest version from the git repository and see if everything works as expected. If there aren't any bug reports by Sept. 18, I am going to make a new release.
Thank you, Vladimir
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
I've added all the buggy code examples you've sent so far to the Parenscript test suite, which passes. Send an example of this bug, I think it may be a different issue.
Vladimir
On Mon, Sep 14, 2009 at 10:20 AM, Daniel Gackle danielgackle@gmail.com wrote:
I just ran our regression tests and am noticing one problem: some symbol macros aren't expanding. This seems like it might be the return of a bug I posted about before. I don't have time to post an example at the moment (I can do so later), but thought I should report the issue.
On Sun, Sep 13, 2009 at 4:23 PM, Vladimir Sedach vsedach@gmail.com wrote:
Hi everybody,
I just pushed a bunch of patches greatly improving Parenscript compilation performance, and adding the ability to print Parenscript output directly to a stream. I think it's time to make a release. Please check out the latest version from the git repository and see if everything works as expected. If there aren't any bug reports by Sept. 18, I am going to make a new release.
Thank you, Vladimir
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
The version we're using (4cc463) does this:
(ps (define-symbol-macro blah 10) (fn blah))
=> "fn(10);"
The latest version (2471a2) does this:
(ps (define-symbol-macro blah 10) (fn blah))
=> "fn(blah);"
On Tue, Sep 15, 2009 at 7:57 AM, Vladimir Sedach vsedach@gmail.com wrote:
I've added all the buggy code examples you've sent so far to the Parenscript test suite, which passes. Send an example of this bug, I think it may be a different issue.
Vladimir
On Mon, Sep 14, 2009 at 10:20 AM, Daniel Gackle danielgackle@gmail.com wrote:
I just ran our regression tests and am noticing one problem: some symbol macros aren't expanding. This seems like it might be the return of a bug
I
posted about before. I don't have time to post an example at the moment
(I
can do so later), but thought I should report the issue.
On Sun, Sep 13, 2009 at 4:23 PM, Vladimir Sedach vsedach@gmail.com
wrote:
Hi everybody,
I just pushed a bunch of patches greatly improving Parenscript compilation performance, and adding the ability to print Parenscript output directly to a stream. I think it's time to make a release. Please check out the latest version from the git repository and see if everything works as expected. If there aren't any bug reports by Sept. 18, I am going to make a new release.
Thank you, Vladimir
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
I just pushed a patch for this bug (it was related to how symbols were treated at the top-level and exposed some subtle bugs with how the compiler currently works - I didn't like the revelation of the latter issue). Unless there are more objections, I think I'll go ahead with a release.
Vladimir
On Tue, Sep 15, 2009 at 11:41 AM, Daniel Gackle danielgackle@gmail.com wrote:
The version we're using (4cc463) does this:
(ps (define-symbol-macro blah 10) (fn blah))
=> "fn(10);"
The latest version (2471a2) does this:
(ps (define-symbol-macro blah 10) (fn blah))
=> "fn(blah);"
On Tue, Sep 15, 2009 at 7:57 AM, Vladimir Sedach vsedach@gmail.com wrote:
I've added all the buggy code examples you've sent so far to the Parenscript test suite, which passes. Send an example of this bug, I think it may be a different issue.
Vladimir
On Mon, Sep 14, 2009 at 10:20 AM, Daniel Gackle danielgackle@gmail.com wrote:
I just ran our regression tests and am noticing one problem: some symbol macros aren't expanding. This seems like it might be the return of a bug I posted about before. I don't have time to post an example at the moment (I can do so later), but thought I should report the issue.
On Sun, Sep 13, 2009 at 4:23 PM, Vladimir Sedach vsedach@gmail.com wrote:
Hi everybody,
I just pushed a bunch of patches greatly improving Parenscript compilation performance, and adding the ability to print Parenscript output directly to a stream. I think it's time to make a release. Please check out the latest version from the git repository and see if everything works as expected. If there aren't any bug reports by Sept. 18, I am going to make a new release.
Thank you, Vladimir
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
I ran our regression tests, can confirm the fix and am not seeing any new bugs.
I also just pushed a couple of minor commits that add &REST and &OPTIONAL to the PS version of DESTRUCTURING-BIND. Let me know if you don't want them in the release (or just release your last patch, 8785789).
Daniel
On Fri, Sep 18, 2009 at 12:42 PM, Vladimir Sedach vsedach@gmail.com wrote:
I just pushed a patch for this bug (it was related to how symbols were treated at the top-level and exposed some subtle bugs with how the compiler currently works - I didn't like the revelation of the latter issue). Unless there are more objections, I think I'll go ahead with a release.
Vladimir
On Tue, Sep 15, 2009 at 11:41 AM, Daniel Gackle danielgackle@gmail.com wrote:
The version we're using (4cc463) does this:
(ps (define-symbol-macro blah 10) (fn blah))
=> "fn(10);"
The latest version (2471a2) does this:
(ps (define-symbol-macro blah 10) (fn blah))
=> "fn(blah);"
On Tue, Sep 15, 2009 at 7:57 AM, Vladimir Sedach vsedach@gmail.com
wrote:
I've added all the buggy code examples you've sent so far to the Parenscript test suite, which passes. Send an example of this bug, I think it may be a different issue.
Vladimir
On Mon, Sep 14, 2009 at 10:20 AM, Daniel Gackle <danielgackle@gmail.com
wrote:
I just ran our regression tests and am noticing one problem: some
symbol
macros aren't expanding. This seems like it might be the return of a
bug
I posted about before. I don't have time to post an example at the
moment
(I can do so later), but thought I should report the issue.
On Sun, Sep 13, 2009 at 4:23 PM, Vladimir Sedach vsedach@gmail.com wrote:
Hi everybody,
I just pushed a bunch of patches greatly improving Parenscript compilation performance, and adding the ability to print Parenscript output directly to a stream. I think it's time to make a release. Please check out the latest version from the git repository and see
if
everything works as expected. If there aren't any bug reports by
Sept.
18, I am going to make a new release.
Thank you, Vladimir
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
parenscript-devel@common-lisp.net
-
Daniel Gackle -
Vladimir Sedach