octave-maintainers
[Top][All Lists]
Advanced

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

Re: Dropping octave's native image format


From: Rik
Subject: Re: Dropping octave's native image format
Date: Sat, 13 Jul 2013 14:11:57 -0700

On 07/13/2013 09:04 AM, address@hidden wrote:
> Message: 2
> Date: Sat, 13 Jul 2013 11:11:46 +0200
> From: S?ren Hauberg <address@hidden>
> To: Carn? Draug <address@hidden>
> Cc: address@hidden
> Subject: Re: Dropping octave's native image format
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=iso-8859-1
>
> On Jul 13, 2013, at 3:24 AM, Carn? Draug <address@hidden> wrote:
>> > This is what I figured by reading the source of imread. As far as can
>> > see, this format is completely undocumented, and we don't even have a
>> > function to write into it. Should we remove this? I'm guessing that
>> > even if we removed it, no one would notice (except for when calling
>> > image() without arguments since it loads default.img, the only example
>> > I have of an image in this format).
> This is from back before Octave had 'imread' and 'imwrite'. Then we had the 
> functions 'loadimage' and 'saveimage' .
>
> Is there any maintenance burden in supporting this old format? I guess it is 
> quite unused, but if it doesn't hurt to keep supporting it, then I don't see 
> a reason to remove it. If it makes it harder to evolve the code to support 
> this, then I think it's fine to drop it.
>
> S?ren
I would take the code out.  The functions loadimage and saveimage were
removed before 3.6 so there's no good way to access this data type.

I think it is sort of like your appendix which is generally fine to have
around until, on the odd occasion, it gets inflames, bursts, and puts you
in the hospital.  In this case we could leave the appendix code in place,
but one day it might burst.  And leaving it in I think will also be
confusing to anyone else who stumbles over this code at a later date.  Only
someone like Soren, with a long history with Octave, had any clue what this
was supposed to do.

--Rik


reply via email to

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