Quick Search
Browse
Pages
Blog
Labels
Attachments
Mail
Advanced
What’s New
Space Directory
Feed Builder
Keyboard Shortcuts
Confluence Gadgets
Log In
Sign Up
Dashboard
Clojure Design
Copy Page
You are not logged in. Any changes you make will be marked as
anonymous
. You may want to
Log In
if you already have an account. You can also
Sign Up
for a new account.
This page is being edited by
.
Paragraph
Paragraph
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Preformatted
Quote
Bold
Italic
Underline
Colour
More colours
Strikethrough
Subscript
Superscript
Monospace
Clear Formatting
Bullet list
Numbered list
Outdent
Indent
Align left
Align center
Align right
Link
Table
Insert
Insert Content
Image
Link
Attachment
Symbol
Emoticon
Wiki Markup
Horizontal rule
tinymce.confluence.insert_menu.macro_desc
Info
JIRA Issue
Status
Gallery
Tasklist
Table of Contents
Other Macros
Undo
Redo
Keyboard Shortcuts Help
<h3>Rationale</h3> <p>The Clojure compiler is currently a large Java class. Writing it in Clojure will produce many benefits.</p> <h3>Plan</h3> <ul> <li>Provide discrete analysis phase yielding Clojure data structures capturing semantics of code.</li> <li>Split out type reflection into API <ul> <li>needs protocols to hide actual reflection classes <ul> <li>since we would like to fabricate class and method descriptors for classes-being-compiled</li> </ul> </li> </ul> </li> <li>Split out code gen into API</li> <li>Split off ASM into separate jar <ul> <li>allow for full use of ASM <ul> <li>e.g. show assembly output mode for compiler</li> </ul> </li> <li>this split could happen pre-CinC</li> <li>Should we still re-root package to avoid conflicts?</li> </ul> </li> <li>Multiple back ends <ul> <li>Java source</li> <li>Java bytecode</li> <li>CLR</li> <li>JS</li> <li>?</li> </ul> </li> <li>Remove warts from current design <ul> <li>e.g. use of vars and binding</li> <li>explicitly pass environment <ul> <li>current code modifies environment to e.g. tag things as closed-over <ul> <li>could turn into query against child tree</li> <li>in any case, will need to take and return environment (in addition to returning expression object)</li> </ul> </li> </ul> </li> <li>some rewriting is done during analysis in order to facilitate generation <ul> <li>e.g. wrapping things in lambdas to get around expression restrictions</li> <li>should/could this be done later, during gen? <ul> <li>since different targets might have different approaches</li> </ul> </li> </ul> </li> </ul> </li> <li>Some impacts on current infrastructure <ul> <li>e.g. namespaces map to vars or classes <ul> <li>need to map to class descriptors in order to be able to resolve to things-being-compiled</li> </ul> </li> </ul> </li> </ul> <h3>Issues</h3>
Attachments
Labels
Location
< Edit
Preview >
Loading…
Save
Cancel
Next hint
search
attachments
weblink
advanced