From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: A macro and an unwanted containing list in the resulting form
Date: Thu, 24 May 2007 18:47:50 +1000 [thread overview]
Message-ID: <87lkfe7gll.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.1113.1179959874.32220.help-gnu-emacs@gnu.org
Sebastian Tennant <sebyte@smolny.plus.com> writes:
> Quoth Pascal Bourguignon <pjb@informatimago.com>:
>> Sebastian Tennant <sebyte@smolny.plus.com> writes:
>>>> Is there any reason to make the argument of build-cond an alist? You
>>>>could try
>>>>
>>>> (defmacro build-cond (&rest conds)
>>>> (append '(cond)
>>>> (mapcar '(lambda (each)
>>>> (cons (list 'equal 'my-var (car each)) (list (cdr each))))
>>>> conds)))
>>>>
>>>> and then use
>>>>
>>>> (build-cond ("hello" . (message "hi"))
>>>> ("goodbye" . (message "bye"))
>>>
>>> The reason for the alist is the clauses are being passed as one of a
>>> number of arguments to a function call.
>>
>> If you get the a-list as argument to a function, then you don't need a
>> macro to process it! Just write a loop!
>>
>> (require 'cl)
>>
>> (defun my-function (string clauses)
>> (loop
>> for clause in clauses
>> until (string= string (car clause))
>> finally (eval (cdr clause))))
>>
>> (my-function "goodbye" '(("hello" . (message "hi"))
>> ("goodbye" . (message "bye"))))
>>
>
> Whoa! This isn't LISP! At least it doesn't look like it to me.
> Where are the parentheses? I suppose I haven't got the first idea how
> the Common Lisp 'loop' function works...???
>
> Sebastian
>
You aren't the first to make those comments. CL's loop is one area that
generally creates considerable debate - som argue its not lispy and is
difficult to master. Others argue its a very powerful construct that shows what
you can do with CL.
I'm still pretty much a novice with CL and will admit that loop and format (the
CL version) are two aspects of CL that took considerably more mental effort to
understand. I now now reasonably confident with using format, though I
constantly have to check the references. Loop on the other hand is still a
concept I get amazed by and one I have a lot more work to do with before I can
honestly say I'm confident with. However, like most of the stuff I've done with
CL, its been one of the most rewarding languages I've learnt for many many
years. I also find the different development style of working in CL extremely
rewarding after years of C, C++, Java, Tcl and Perl. I now find I've gotten to
the point that its productive for me to 'explore' a problem with CL before I
start implementing the solution in another (more readily accepted) language.
This process often exposes subtle issue that are not evident when working on a
solution from an abstract level and I'm finding it saves me time refactoring or
redesigning things to accomadate the increased understanding that occurs as you
work on a problem.
Tim
--
tcross (at) rapttech dot com dot au
next prev parent reply other threads:[~2007-05-24 8:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 11:28 A macro and an unwanted containing list in the resulting form Sebastian Tennant
2007-05-23 11:39 ` Juanma Barranquero
2007-05-23 12:51 ` Sebastian Tennant
2007-05-23 13:14 ` Juanma Barranquero
2007-05-23 21:40 ` Sebastian Tennant
[not found] ` <mailman.1069.1179924576.32220.help-gnu-emacs@gnu.org>
2007-05-23 16:57 ` Pascal Bourguignon
2007-05-23 21:45 ` Sebastian Tennant
[not found] ` <mailman.1113.1179959874.32220.help-gnu-emacs@gnu.org>
2007-05-24 8:47 ` Tim X [this message]
2007-05-24 13:49 ` Sebastian Tennant
2007-05-24 16:12 ` Johan Bockgård
[not found] <mailman.1062.1179919591.32220.help-gnu-emacs@gnu.org>
2007-05-23 12:04 ` Pascal Bourguignon
2007-05-23 21:32 ` Sebastian Tennant
[not found] ` <mailman.1104.1179956594.32220.help-gnu-emacs@gnu.org>
2007-05-23 23:48 ` Pascal Bourguignon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lkfe7gll.fsf@lion.rapttech.com.au \
--to=timx@nospam.dev.null \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).