<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><a href="http://www.offcenterdesigns.net/wp-content/uploads/wp-checkout/images/i-found-the-i-in-team-t-shirt-1344970569.jpg">http://www.offcenterdesigns.net/wp-content/uploads/wp-checkout/images/i-found-the-i-in-team-t-shirt-1344970569.jpg</a></div><div><br></div><div>I think the problem with macros in general is that their semantics is defined purely in terms of code they generate. Not in terms of what that code actually does. As for me, I want to think about the things I need to achieve, not about the code to write.</div><div><br></div><div><div>Az iPademről küldve</div></div><div><br>2017. ápr. 19. dátummal, 6:24 időpontban Richard A. O'Keefe <<a href="mailto:ok@cs.otago.ac.nz">ok@cs.otago.ac.nz</a>> írta:<br><br></div><blockquote type="cite"><div><span></span><br><blockquote type="cite"><span>On 19/04/2017, at 3:13 PM, Atrudyjane via Haskell-Cafe <<a href="mailto:haskell-cafe@haskell.org">haskell-cafe@haskell.org</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I used to, mainly C/C++. There is no "I" in team... Our personalities must be similar : )</span><br></blockquote><span></span><br><span>It's hidden, but there is definitely "a me" in "team".</span><br><span>And then it's time for "T". (Obscure Lisp reference.)</span><br><span></span><br><span>Someone wrote:</span><br><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>I think Lisp-style macros are too powerful.</span><br></blockquote></blockquote></blockquote><span></span><br><span>It's true that higher-order functions can do a lot of the things people used</span><br><span>macros to do, and better.</span><br><span></span><br><span>However, having said "Lisp-style macros", Lisp is a tree with many branches.</span><br><span>How about Scheme-style macros?</span><br><span></span><br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Problem with that is that empowering the programmer makes it harder to be 100% sure what a given piece of code does.</span><br></blockquote></blockquote></blockquote><span></span><br><span>This is also true in Haskell. Show me a piece of code golf with Arrows and</span><br><span>LemurCoSprockets and such all over the place and I haven't a clue. Total</span><br><span>bewilderment. Heck, show me *undocumented* code in a language without</span><br><span>macros, classes, or higher-order functions (Fortran 95? COBOL 85?) and I'll</span><br><span>be just as baffled, if it is big enough. (I've been staring at some old</span><br><span>numeric code recently. One page is quite big enough...)</span><br><span></span><br><span></span><br><span></span><br><span>_______________________________________________</span><br><span>Haskell-Cafe mailing list</span><br><span>To (un)subscribe, modify options or view archives go to:</span><br><span><a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe">http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe</a></span><br><span>Only members subscribed via the mailman list are allowed to post.</span></div></blockquote></body></html>