[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: adopting functions from Octave-forge
From: |
Andy Adler |
Subject: |
Re: adopting functions from Octave-forge |
Date: |
Thu, 29 Sep 2005 21:52:56 -0400 (EDT) |
John,
I have begin looking at adapting some files from
your list for inclusion in octave. As I understand it,
the coding style needs to match octave's.
I've modified conv2.cc. Could you take a look to see if I
need to do anything else?
http://cvs.sourceforge.net/viewcvs.py/octave/octave-forge/main/image/conv2.cc?rev=HEAD
If this is acceptable, they I'll go any modify my other
code.
--
Andy Adler <address@hidden> 1(613)562-5800x6218
On Thu, 29 Sep 2005, John W. Eaton wrote:
> Is anyone maintaining a list of functions that have been moved from
> Octave to Octave-forge? If so, where is it kept? I'd like to add to
> it as more functions are adopted.
>
> Ignoring sparse functions, we currently have the following overlap:
>
> builtin dispatch hankel mu2lin randn struct
> cellstr dispatch_help isa ndims rmfield tf2zp
> char double isequal orient setdiff toeplitz
> chol fieldnames isfield polyder sortrows tril
> complex full ismember polyderiv str2double triu
> deal gammaln issparse polygcd strcmpi unique
> detrend gammaln isunix print strmatch unix
> dispatch grid lin2mu rand strncmp zp2tf
>
> Some of these may still be different in Octave-forge, so the list
> should also keep the current status of the function so that we don't
> end up with two diverging versions of each of these.
>
> jwe
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>