[parenscript-devel] Breaking up js.lisp
![](https://secure.gravatar.com/avatar/e42f6c21cb1b7d45ec30570df35cbee9.jpg?s=120&d=mm&r=g)
Parenscript is long overdue for a simple code reorganization. js.lisp is a monolithic file with nearly all the interesting components of the compiler. I propose splitting it up into three different files: source-model.lisp, js-translation.lisp, and parser.lisp: source-model.lisp: class definitions that correspond to the Javascript AST. (defjsclass forms for the most part) js-translation.lisp: functions for converting AST objects to Javascript source code parser.lisp: macro definitions and the mechanisms for processing Parenscript forms into AST objects. Let me know if there are any objections. Otherwise I will go ahead and submit a patch. Red
![](https://secure.gravatar.com/avatar/6a2a0564e2c584c8e9fa1ec369bd23e0.jpg?s=120&d=mm&r=g)
That sounds like a great idea. Pull the latest patch from the main repository though - I made changes to most of js.lisp today. Also, let me know if you want push access to the repository - maybe that will speed up changes a little bit. Thanks, Vladimir On 6/26/07, Red Daly <reddaly@gmail.com> wrote:
Parenscript is long overdue for a simple code reorganization. js.lisp is a monolithic file with nearly all the interesting components of the compiler. I propose splitting it up into three different files: source-model.lisp , js-translation.lisp, and parser.lisp:
source-model.lisp: class definitions that correspond to the Javascript AST. (defjsclass forms for the most part)
js-translation.lisp: functions for converting AST objects to Javascript source code
parser.lisp: macro definitions and the mechanisms for processing Parenscript forms into AST objects.
Let me know if there are any objections. Otherwise I will go ahead and submit a patch.
Red
_______________________________________________ parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
![](https://secure.gravatar.com/avatar/e42f6c21cb1b7d45ec30570df35cbee9.jpg?s=120&d=mm&r=g)
Great. I sent you a patch that incorporates your changes and splits up js.lisp. -red On 6/26/07, Vladimir Sedach <vsedach@gmail.com> wrote:
That sounds like a great idea. Pull the latest patch from the main repository though - I made changes to most of js.lisp today. Also, let me know if you want push access to the repository - maybe that will speed up changes a little bit.
Thanks, Vladimir
On 6/26/07, Red Daly <reddaly@gmail.com> wrote:
Parenscript is long overdue for a simple code reorganization. js.lispis a monolithic file with nearly all the interesting components of the compiler. I propose splitting it up into three different files: source-model.lisp, js-translation.lisp, and parser.lisp:
source-model.lisp: class definitions that correspond to the Javascript AST. (defjsclass forms for the most part)
js-translation.lisp: functions for converting AST objects to Javascript source code
parser.lisp: macro definitions and the mechanisms for processing Parenscript forms into AST objects.
Let me know if there are any objections. Otherwise I will go ahead and submit a patch.
Red
_______________________________________________ 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
![](https://secure.gravatar.com/avatar/6a2a0564e2c584c8e9fa1ec369bd23e0.jpg?s=120&d=mm&r=g)
Ok, Red's patch is now in the darcs repository; js.lisp is no more. Vladimir On 6/26/07, Red Daly <reddaly@gmail.com> wrote:
Great. I sent you a patch that incorporates your changes and splits up js.lisp.
-red
On 6/26/07, Vladimir Sedach < vsedach@gmail.com> wrote:
That sounds like a great idea. Pull the latest patch from the main repository though - I made changes to most of js.lisp today. Also, let me know if you want push access to the repository - maybe that will speed up changes a little bit.
Thanks, Vladimir
On 6/26/07, Red Daly < reddaly@gmail.com> wrote:
Parenscript is long overdue for a simple code reorganization. js.lisp is a monolithic file with nearly all the interesting components of the compiler. I propose splitting it up into three different files: source-model.lisp , js-translation.lisp, and parser.lisp:
source-model.lisp: class definitions that correspond to the Javascript AST. (defjsclass forms for the most part)
js-translation.lisp: functions for converting AST objects to Javascript source code
parser.lisp: macro definitions and the mechanisms for processing Parenscript forms into AST objects.
Let me know if there are any objections. Otherwise I will go ahead and submit a patch.
Red
_______________________________________________ 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
participants (2)
-
Red Daly
-
Vladimir Sedach