octave-maintainers
[Top][All Lists]
Advanced

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

Re: problems to be fixed before next snapshot


From: John W. Eaton
Subject: Re: problems to be fixed before next snapshot
Date: Wed, 23 Oct 2002 13:46:26 -0500

On 23-Oct-2002, Paul Kienzle <address@hidden> wrote:

| Should we extend all of our primitives to handle cell arrays?  
| 
| E.g., is f({A, B, C}) == {f(A), f(B), f(C)} for all of our mappers?
| 
| How about functions which operate on arrays?  Is 
| 
|       [Q,R]=qr({A,B,C}) 
| 
| equivalent to 
| 
|       X={A,B,C}; 
|       for i=1:length(X), 
|           [Q{i}, R{i}] = qr(X{i}) 
|       end

Probably just about as good to have an "apply" function for this (and
certainly less work to implement!).

| > to pass the elements of the comma-separated list as separate arguments
| > to the function foo, but you can't write
| > 
| >   y = x.a
| > 
| > to capture the elements of the comma-separated list in a single
| > variable.
| 
| But can you write the following?
| 
|       y = { x.a }

Yes.  I had forgotten about that.  This is another change that is
needed for Octave's parser.

jwe



reply via email to

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