[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ellipse
From: |
Søren Hauberg |
Subject: |
Re: ellipse |
Date: |
Sat, 31 Jan 2009 20:02:51 +0100 |
lor, 31 01 2009 kl. 12:33 -0500, skrev John W. Eaton:
> On 31-Jan-2009, Soren Hauberg wrote:
>
> | Ok. How about
> |
> | ellipse (a, shift, level, n, ...)
> |
> | ? I guess that orders the input arguments by how important they are.
>
> I think the relative order is subjective. So I don't really see a
> good reason for changing from the original ordering.
I don't entirely agree with the ordering being subjective, but this is
really no big deal, so I've used the original ordering.
> Another option is to keep them in the original ordering but allow an
> empty matrix to be used as a placeholder that means "use the default
> value". Then you could write
>
> ellipse (a, [], [], shift);
>
> is that an acceptable compromise?
The function is implemented using default arguments, so you can do
ellipse (a, :, :, shift)
It's even documented :-)
Soren
ellipse.changeset
Description: Text document
- ellipse, John W. Eaton, 2009/01/29
- Re: ellipse, Søren Hauberg, 2009/01/30
- Re: ellipse, John W. Eaton, 2009/01/30
- Re: ellipse, Søren Hauberg, 2009/01/31
- Re: ellipse, John W. Eaton, 2009/01/31
- Re: ellipse, Søren Hauberg, 2009/01/31
- Re: ellipse, John W. Eaton, 2009/01/31
- Re: ellipse, Kai Habel, 2009/01/31
- Re: ellipse, Søren Hauberg, 2009/01/31
- Re: ellipse, Kai Habel, 2009/01/31
- Re: ellipse,
Søren Hauberg <=
- Re: ellipse, Daniel J Sebald, 2009/01/31