Re: [OctDev] Re: [Octave-cvsupdate] octave-forge/main/image imread.m,1.11,1.12 imwrite.m,1.8,1.9

[Paul K. <pki...@us...>]

On Jul 26, 2005, at 9:43 PM, Andy Adler wrote:

> On 7/26/05, Stefan van der Walt <st...@su...> wrote:
>> Please see the attached imread2.m, pngread.cc etc.
>>
>> The only thing to note about these is that they already return colour
>> images in the MxNx3 format.  Octave 2.9 branch supports showing these,
>> but many other functions don't (yet).  I don't think this should be a
>> problem if I provide an im2gray function, though.
>
> In my opinion, you should commit these. Imread2 should replace
> imread. As we move to Octave 3.0, now is the time to clean out cruft
> like imread returning parameters compatible with matlab 4.
>
> Do any others have opinions on this?

It would be nice to support old and new versions of Matlab's 
ever-changing API so that as much as possible code just works.  
However, with nobody willing do do the work, I agree that dropping the 
Matlab 4 support is the best path forward.  Someday somebody who cares 
can implement a v4 wrapper on functions which have changed.

- Paul