Thank you very much Aaron, for all your help ! I contacted David Nolen via twitter, because i couldn't find an email address, i'm gonna contact him via IRC right now.
About your questions : > In your Python-to-Lua compiler, you ran into problems with limitations in the semantics of Lua. Why is this not going to be a problem with Clojure-to-Lua? Well it *could* be a problem, since Clojure has different semantics regarding number types. But clojurescript already settled that problem by adopting Javascript semantics regarding that. Also, Lua and Javascript have very similar semantics regarding numbers, so that's another plus in my opinion. Everything beyond number types can be adapted to fit to Clojure semantics without too much of a performance hit, the same way it has been done for Javascript. I'm not sure this is worth mentionning in the application, since it is very much an implementation detail, and not very likely to be a problem. What do you think ? > Why choose a source-to-source compiler, rather than one emitting Lua bytecode? I'm not saying one is better than the other, I'm just asking the question, and suggesting that it may or may not be worth mentioning in your proposal. Well the main reason is that LuaJIT uses a different and incompatible bytecode format, and since being able to execute on LuaJIT is a key goal of my project, i was thinking of doing a source to source compiler. More generally, there is literally a plethora of Lua interpreters and compilers, and compiling to sources gives you the ability to use any of them. For example lua-llvm can compile native binaries, and it would be an interresting path to native executables. You're right that i should mention that in my application, i'm gonna add that ASAP :) > Are you familiar with how code is submitted to Clojure? Do you have a CA on file? Do you know that the patches are going to be used rather than git pulls? Well i've read the http://clojure.org/contributing page, and reviewed the CA. I think i can work via git and use the "JIRA patch" way for the final submission. What do you think ? > It should be a goal of your project that your code be integrated back into ClojureScript, not just end up as an orphaned fork. But, don't make it a condition for success. Well that is indeed my goal, and i really hope that i will be able to contribute positively to the Clojure project ! > I left the parts where you talk about "not being the most experienced Clojure developer around in" because I felt like removing them was too heavy an editor's hand. I'd recommend you think about removing them though. You're not really expected to be the most experienced Clojure developer around, and it doesn't convey much information. Ok i will probably remove them then :) Thank you again, you have really helped me through this, and i'm very grateful ! On Thursday, April 5, 2012 9:54:11 PM UTC+2, Aaron Cohen wrote: > > This looks _much_ better, Raphael. > > My next suggestion would be trying to contact dnolen directly, either via > email or (preferably) on IRC so that he can have an opportunity to give you > feedback. Tomorrow is the deadline, so I'm going ahead and doing an edit at > the moment. I'll send a pull request shortly. > > Questions: > > In your Python-to-Lua compiler, you ran into problems with limitations in > the semantics of Lua. Why is this not going to be a problem with > Clojure-to-Lua? > > Why choose a source-to-source compiler, rather than one emitting Lua > bytecode? I'm not saying one is better than the other, I'm just asking the > question, and suggesting that it may or may not be worth mentioning in > your proposal. > > How will you measures the success of your project? Are you planning to do > any performance testing or verification of the resulting compiler? > > Are you familiar with how code is submitted to Clojure? Do you have a CA > on file? Do you know that the patches are going to be used rather than git > pulls? > > It should be a goal of your project that your code be integrated back into > ClojureScript, not just end up as an orphaned fork. But, don't make it a > condition for success. > > I left the parts where you talk about "not being the most experienced > Clojure developer around in" because I felt like removing them was too > heavy an editor's hand. I'd recommend you think about removing them though. > You're not really expected to be the most experienced Clojure developer > around, and it doesn't convey much information. > > I just sent you a pull request, good luck on your application! > > --Aaron > > 2012/4/5 Raphaël AMIARD <raph.ami...@gmail.com> > >> Sorry about that, i messed up the link for the application ... >> >> ClojureScript to Lua >> Application<http://raph-amiard.github.com/ClojureScriptLua.html> >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clojure@googlegroups.com >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en >> > > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
