Re: [ANN] ClojureC 0.1
On Monday, April 22, 2013 6:18:56 PM UTC-7, John Gabriele wrote: I'm curious: what (if any) differences do you see happening between Clojure(Script) and ClojureC? How close do you expect them to be? I'd like them to be as close as reasonably possible. Some differences that exist today are * Fields can only be accessed in code following the types they declare. I'm not too happy about this, but can't be bothered to fix it right now. * Non-mutable fields cannot be set. That's a feature. * Only declared protocol methods can be implemented, i.e. you can't make up a new method for a type, implement it and call it. * Integers are not floats and vice versa. * Characters are not strings. Do you have any notions yet of what C-library interop might look like? Not really. Right now a low-level interface to C exists, similar to ClojureScript's `js*`, namely `c*`, but that's probably not what you'd want to use for binding on a larger scale. We might co-opt SWIG. Mark -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[ANN] ClojureC 0.1
Dear Clojurians, I'm happy to announce ClojureC 0.1: https://github.com/schani/clojurec ClojureC is a Clojure to C compiler that's based off of ClojureScript. It's still in its infancy, not ready for real use, but at this point almost all of ClojureScript's core library has been ported - most of it without needing any modification. If you're interested in contributing, here are a few things we need to make ClojureC useful, in order of difficulty: * Regular expressions - probably by binding PCRE or something similar. * I/O of all kinds - file, network * A somewhat generic method for binding C libraries * A debugger * Better generated C code - right now it's very inefficient, but there's lots of low-hanging fruit. Cheers! Mark -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
ICFP Contest in ClojureC
Hey ho! If anybody's up for entering the ICFP programming contest http://icfpcontest2012.wordpress.com/task/ with a ClojureC program, email me mark.probst at gmail Obviously most of the work would be getting ClojureC up to the task :-) Mark -- 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
Re: ClojureC - A Clojure to C compiler - Work in Progress
Adam, Just a quick iOS update. I grabbed the latest from your git repo and from my initial work at implementing the required glib methods that you're using, I now have it running on both my iPad and iPhone4S. I don't look at the glib source - I just google the missing function name and implement it based on what the docs describe. It spits out (to the debug console) the same output as OSX shows when running ./cljc from the Terminal, which would be: (4 5) That's fantastic news! Reimplementing the glib string functions is not the way to go for iOS, but I understand why you did it in the first iteration. As I said, we'll have proper Objective-C bindings which will make those things much better. As you can see, there are some Unused variable 'env' and Expression result unused warnings which I'll probably just disable. Yes, they're just a result of the compiler being very simple-minded, and they do no harm. I'll clean it up and commit to my github clojurec repo branch and then I'll do a pull request later this weekend/Monday. I'll also pop my signed Clojure Contribution Agreement in the mail tomorrow incase that's needed. I'll have to figure out how to handle this, too. Thanks for reminding! Mark -- 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
