Re: [OctDev] convhulln options.

[Rafael L. <lab...@ps...>]

* Paul Kienzle <pki...@us...> [2003-12-09 08:39]:
 
> On Dec 9, 2003, at 8:21 AM, Rafael Laboissiere wrote:
>
> >Currently, the delaunay* functions of octave-forge have definitions 
> >similar
> >to this:
> >
> >    T = delaunayn (P[, OPT])
> >
> >where OPT is a string of options to be passed to the underlying qhull
> >command.  I was thinking about extending the above to the voronoi* and
> >convhull* functions.  Would it be okay?
> 
> Okay, but I would prefer 'standard' option handling.  Problem is, I
> don't like the matlab standard: f(...,'option',val).  Passing a 
> structure
> x with fields option=value would be okay if octave had a syntax for
> structure constants.

I do not follow you.  The OPT argument of the delaunay* function is a simple
string containing options to be passed to the qhull command.  for instance,
one may call:

    T = delaunayn (P, "Qt")

What does this have to do with the pairs <'option', val> that you 
mentioned?

-- 
Rafael