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

[Pkg-octave-devel] Bug#626264: Bug#626264: Bug#626264: octave-miscellaneous: Please upload new upstream (1.0.11) release



On 10 May 2011 14:51, Thomas Weber <tweber@debian.org> wrote:
> On Tue, May 10, 2011 at 01:54:24PM +0200, Didier Raboud wrote:
>> Package: octave-miscellaneous
>> Version: 1.0.9-1+b1
>> Severity: minor
>>
>> Hi,
>>
>> octave-optim, in it 1.0.16-1 version, uploaded on 23. April, depends on
>> octave-miscellaneous >= 1.0.11, so please upload it to allow the installation
>> of octave-optim/unstable.
>
> From miscellaneous 1.0.11:
> [map]
>  ***** test
>  assert(map(@min,[1 2 3 4 5],[5 4 3 2 1]), [1 2 3 2 1])
>  assert(map(@min,rand(1,5),[0 0 0 0 0]), [0 0 0 0 0])
>  assert(map(@(x,y) (sin(x).^2 + cos(y).^2),-pi:0.5:+pi,-pi:0.5:+pi),ones(1,13))
> !!!!! test failed
> assert (map (@(x, y) (sin (x) .^ 2 + cos (y) .^ 2);
> , -pi:0.5:+pi, -pi:0.5:+pi),ones (1, 13)) expected
>   1   1   1   1   1   1   1   1   1   1   1   1   1
> but got
>   1   1   1   1   1   1   1   1   1   1   1   1   1
>
>
> The problem is that Octave 3.2 isn't consistent in what ones() returns:
> ...
> GNU Octave, version 3.2.4
> ...
> octave:1> typeinfo(ones(1,13))
> ans = range
> octave:2> typeinfo(ones(2,13))
> ans = matrix
>
> I don't have the build power on my notebook to build 3.4. Can you check wether
> this has changed there?
>

     octave:1> typeinfo(ones(1,2))
     ans = range
     octave:2> typeinfo(ones(2,2))
     ans = matrix
     octave:3> version
     ans = 3.5.0+

But I don't think this is a problem; it's a useful optimisation. The
map function that package should be deprecated anyways, we have
arrayfun instead if you really need that kind of functionality. In
fact, the assert that fails works if you simply do s/map/arrayfun/.

- Jordi G. H.





Reply to: