oject (no matter how short it is)
starts by writing raw code, and then, when I see what is being done
often, replacing parts with macros that simplify the code and make it
easier to read.
Mirko
--~--~-~--~~~---~--~~
You received this message because you are subscri
On Feb 22, 3:14 pm, Mark Volkmann wrote:
> On Sun, Feb 22, 2009 at 1:54 PM, Mirko wrote:
> > In my practice, almost every project (no matter how short it is)
> > starts by writing raw code, and then, when I see what is being done
> > often, replacing parts with macros t
On Feb 22, 6:19 pm, Raffael Cavallaro
wrote:
> On Feb 22, 2:54 pm, Mirko wrote:
>
>
>
> > In lisp you would define it as (untested):
>
> > (defmacro print-times (reps text)
> > `(do-times (i ,reps)
> > (print ,text))
>
> > (Not trying to forc
ever to load.
Thank you,
Mirko
--~--~-~--~~~---~--~~
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 [EMA
ably use ClojureScript instead of Clojure for the
> client-side code, but I haven't done that yet.
>
> --Chouser
That is encouraging!
I was staring at the source code to your page, and is the navigation
script in irc.js? (I am probably exposing my ignorance here).
If so, would you mind sh
On Nov 11, 3:08 pm, Chouser <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 11, 2008 at 2:45 PM, Mirko <[EMAIL PROTECTED]> wrote:
>
> > I was staring at the source code to your page, and is the navigation
> > script in irc.js? (I am probably exposing my ignoranc
