Hello! On 27 Jan., 22:49, Raoul Duke <rao...@gmail.com> wrote: > On Wed, Jan 27, 2010 at 1:41 PM, Matt Revelle <mreve...@gmail.com> wrote: > > In general, if you see a form that looks like it's a special language > > and wouldn't evaluate its > > contents before executing the form then it's a macro. > > but that is a chicken-egg thing where i have to experiment and fiddle > and then memorize special cases before i can get things working right. > in the mean time i'm facing a bunch of possible ways to do something > and most won't work (and some even don't work w/out giving anything > that is an error!) and my psyche has to go through a lot of the > programming language basically telling me "eff you, luser!".
Well, there are some things that can quickly be identified as macros, like the various def* or with-* forms. Besides, in every language there are some things one will have to get used to and which may seem odd at first sight. One major difference of languages like Clojure is that (assuming a proper environment to work in) a quick check at the REPL is only some fraction of a second away, and the few stumbling blocks like #'and shouldn't be a real problem if you try to learn the language seriously for more than one week. > which to me seems somewhat antithetical to didactic purposes. i'm much > more in the TOOWTDI camp than the TMTOWTDI when it comes to design. What if the OWTDI starts to get in your way? Is there anyone capable to define a OWTD which will fit your requirements in the future? Regards dhl -- 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
