Re: Deprecate cut()?

[Judd Storrs]

> On Apr 5, 2010, at 6:49 PM, forkandwait wrote:
> (though a lot of people coming from R/SPLUS or other languages
> might try a cut() function like I did).

Ok, that's slightly different--if the intent of cut() is to be similar
to R then that should be added to the documentation and the bug-fix
should be verified to match what R does. Perhaps we should have an
r_compatibility package on octave-forge.

On Mon, Apr 5, 2010 at 6:39 PM, Ben Abbott <address@hidden> wrote:
> I couldn't find any examples where cut() was being used in the sources. So it 
> doesn't appear deprecating cut() would require much work.

It also isn't used by any m-files in the octave-forge svn repository.

I personally feel like cut() doesn't "fit in" with the rest of the
language very well and doesn't add anything of value over histc()--at
least not enough to justify it's inclusion in the base. Easing porting
of algorithms is a good reason to keep it around somewhere--but only
if it actually matches the behavior with R and it should be labeled as
such. There are a few IDL-ish functions I've wanted to add, too.


--judd