Re: Moving code from octave-forge to octave [Was: polyderiv problem?]

[David Bateman]

I looked at the patches directory of octave-forge and it seems that all 
of the patches here, except one are either already included in the main 
part of octave or superseded by other changes to octave. The only 
remaining patch to consider is M-v-ops-2.1.31.patch that allows the 
extension of ./, .*, etc to allow Matrix by vector arguments. Its not 
clear how this ports to NDArrays, since in fact the NDArray 
generalization means that singleton dimensions in one of the args should 
force the matrix to be duplicated allow that dimension of the other arg.

Do we want to do that? In any case, matlab doesn't support this 
behavior, and it might hid some dimensioning errors from the since 
something like "randn(N,1)+randn(1,N)" would create an N-by-N matrix... 
It is clear however, that the existing patch is of no use as a basis for 
this as it is against an octave version prior to the introduction of 
NDArrays. So all of the patches in octave-forge might be dumped...

Regards
David

--
David Bateman                                address@hidden
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax) 
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary