There's no problem with clojure, the problem is with me: I'm a complete noob in clojure programming =) That's why I asked if anyone wanted to port the game. I'll probably learn more reading someone's idiomatic code than my own bad code. I started this project to learn scala so the final code could probably be done in less than 1000 LOC. Later today I'll commit the code to github and send the link.
> Even if you have to make every > modification inside a dosync using the syntax that you originally > provided, why not write a function that captures that and be done with > it? Or, if you have to, a macro? Because: 1 - there's lot of different states with different semantics and collections, this function/macro would need to be generic and thus take a lot of parameters. 2 - I could made one function to each statefull data structure, anyway would be a lot of code compared to the scala one-liner. 3 - maybe I'm mising something... > Sure, I'd be interested in porting it, would give me a reason to learn > Scala :). The code is simple (except for the generate map algorithm) if you know java and OO =) I don't know if the clojure version will be much more concise than the scala version. Scala is the most "low ceremony" language i found, even more than ruby, but idiomatic clojure is probably more, I think. Regards. Islon On 21 nov, 02:41, Timothy Pratley <[EMAIL PROTECTED]> wrote: > > Step right up folks and place your bet. > > Depends on the implementer, Chouser can do it in 95 LOC --~--~---------~--~----~------------~-------~--~----~ 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 To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
