goals for 3.1

[David Bateman]

John W. Eaton wrote:
>    7. Ensure that all operations which work on dimensions alone
>       (squeeze, numel, triu, etc.) work for all objects and preserve
>       type.  Should these functions all be built-in?  Possibly they
>       should all be provided by the octave_value class interface.
>   

Ok, I see this task as being in three parts, and maybe a zeroth part

0) Identify which functions are concerned. I see the list at the moment
as being triu, tril, squeeze, permute, ipermute, shiftdim, circshift,
reshape,  and resize. I'm not sure I see why numel was in that original
list. Are there any others?

1) Write test code that compares the output of Octave against matlab for
the desired functions and confirm their consistency. Address any issues
in the Octave code. The resize function doesn't exist in matlab so its
not obvious to test this function. The attached code I believe tests all
of the others and compares the behavior with matlab's as thecode is
matlab compatible. The 3.0.0 behavior of all of these functions seems to
be correct.

2) Convert that test code to test/assert framework of Octave for
regression testing. It would be easy to add the attached test code into
the test/ directory. However, the trend is to have the tests embedded in
the code, and that will be an issue, in that all of the tests are much
the same, and distributing the tests into each function will result in
code duplication.

3) Convert these functions to be members of the octave_value class. What
are your thoughts now on this? Should they be members of the
octave_value class? Or can we forgo this?

Regards
David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: testfunc.m
Type: text/x-objcsrc
Size: 2227 bytes
Desc: not available
Url : https://www.cae.wisc.edu/pipermail/octave-maintainers/attachments/20080309/55202cab/attachment-0001.bin