[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Deprecate cut()?

From: Ben Abbott
Subject: Re: Deprecate cut()?
Date: Mon, 05 Apr 2010 19:32:07 -0400

On Apr 5, 2010, at 7:25 PM, Judd Storrs wrote:

>> 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

I admit, I'm more likely to remember to use histc() than cut(). Until today I 
wasn't even aware cut() was available.

I like the idea of an r_compatibility package.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]