edebug and defun* &key

edebug and defun* &key

[Le Wang]

[-- Attachment #1: Type: text/plain, Size: 268 bytes --]

Hi all,

I really like the clarity of defun* forms when specifying optional
parameters.  However, edebug doesn't seem to be able to unserstand these
forms very well.  Has anyone got a workaround?

e.g.

(defun* foo (&optional &key (arg t)))

<M-x>edebug-defun

-- 
Le

[-- Attachment #2: Type: text/html, Size: 407 bytes --]

Re: edebug and defun* &key

[Tassilo Horn]

Le Wang <l26wang@gmail.com> writes:

Hi!

> I really like the clarity of defun* forms when specifying optional
> parameters.
>
> (defun* foo (&optional &key (arg t)))

I don't know about edebug and defun*, but for optional parameters, you
don't need defun*.

  (defun foo (&optional baz bla))

is perfectly valid standard elisp.  For &key, you need defun*.  But
keyword parameters are optional anyway, so your above definition should
read like

  (defun* foo (&key (arg t)))

Bye,
Tassilo

Re: edebug and defun* &key

[Le Wang]

[-- Attachment #1: Type: text/plain, Size: 481 bytes --]

On Fri, Jan 7, 2011 at 10:44 PM, Tassilo Horn <tassilo@member.fsf.org>wrote:

>  (defun foo (&optional baz bla))
>

I'm no lisp expert but something like (foo-func nil nil t nil) is just so
much less clean than (foo-func :truncate-blanks nil).


> is perfectly valid standard elisp.  For &key, you need defun*.  But
> keyword parameters are optional anyway, so your above definition should
> read like
>



>  (defun* foo (&key (arg t)))
>

Bingo.  That fixed it.  Thanks.

-- 
Le

[-- Attachment #2: Type: text/html, Size: 1065 bytes --]

Re: edebug and defun* &key

[Raffaele Ricciardi]

On Jan 7, 3:44 pm, Tassilo Horn <tass...@member.fsf.org> wrote:
> Le Wang <l26w...@gmail.com> writes:
>
> Hi!
>
> > I really like the clarity of defun* forms when specifying optional
> > parameters.
>
> > (defun* foo (&optional &key (arg t)))
>
> I don't know about edebug and defun*, but for optional parameters, you
> don't need defun*.
>
>   (defun foo (&optional baz bla))
>
> is perfectly valid standard elisp.  For &key, you need defun*.  But
> keyword parameters are optional anyway, so your above definition should
> read like
>
>   (defun* foo (&key (arg t)))
>
> Bye,
> Tassilo

Moreover, you shouldn't be mixing &optional and &key:

http://gigamonkeys.com/book/functions.html

Read paragraph "Mixing Different Parameter Types".

Re: edebug and defun* &key

[Tim X]

Le Wang <l26wang@gmail.com> writes:

> Hi all,
>
>
> I really like the clarity of defun* forms when specifying optional parameters.
>  However, edebug doesn't seem to be able to unserstand these forms very well.
>  Has anyone got a workaround?
>
> e.g.
>
> (defun* foo (&optional &key (arg t)))
>
> <M-x>edebug-defun

The defun* is a CL compatibility macro and not a part of standard elisp.
i.e. you have to load the 'cl package to get it. 

Elisp can handle the &optional and &key parameter types in normal defun.
IIRC the only real difference is that elisp cannot set default values
for optional parameters - they are nil if not supplied and thats it. 

When you say edebug does not understand these forms very well, what do
you mean?

Tim

-- 
tcross (at) rapttech dot com dot au

Re: edebug and defun* &key

[Tim X]

Tim X <timx@nospam.dev.null> writes:

> Le Wang <l26wang@gmail.com> writes:
>
>> Hi all,
>>
>>
>> I really like the clarity of defun* forms when specifying optional parameters.
>>  However, edebug doesn't seem to be able to unserstand these forms very well.
>>  Has anyone got a workaround?
>>
>> e.g.
>>
>> (defun* foo (&optional &key (arg t)))
>>
>> <M-x>edebug-defun
>
> The defun* is a CL compatibility macro and not a part of standard elisp.
> i.e. you have to load the 'cl package to get it. 
>
> Elisp can handle the &optional and &key parameter types in normal defun.
> IIRC the only real difference is that elisp cannot set default values
> for optional parameters - they are nil if not supplied and thats it. 
>
> When you say edebug does not understand these forms very well, what do
> you mean?
>
> Tim

Correcting myself - elisp doesn't have &key - a mistake I make all the
time because I'm often moving between elisp and cl and constantly get
some of this mixed up. Sorry for any confusion I caused.

Tim

-- 
tcross (at) rapttech dot com dot au