[Top][All Lists]

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

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

From: Michael Creel
Subject: Re: Moving code from octave-forge to octave [Was: polyderiv problem?]
Date: Wed, 09 Feb 2005 17:56:11 +0100
User-agent: KMail/1.7.2

On Wednesday 09 February 2005 16:50, David Bateman wrote:
> 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

I sent this message to David, but I meant to send it to all, so here it is:

This is a behavior that I have found very useful in languages like Gauss and 
Ox. Maybe it would be possible to allow it only for matrices and vectors, but 
not NDArrays? Or maybe a function would do the job. I attach a quck hack for 
consideration. Michael

Attachment: m_x_v.m
Description: Text Data

reply via email to

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