[Insight-developers] Doc updates for ImageIOBase

[Bill Lorensen]

Steve,

We don't know whether any of our customers use WriteImageInformation
and m_Initialized. Many customers have written their own IMAGE IO
classes and it would not be fair to them to change the API. Since we
have released that code, we cannot remove it.

Bill

On Fri, Jan 2, 2009 at 7:25 PM, Steve M. Robbins <steve at sumost.ca> wrote:
> Thanks so much to Luis for patiently answering my questions in this
> thread.  I believe that I understand the semantics of ImageIOBase
> quite a bit better now.
>
> I've used my new understanding to revise the doxygen comments in
> itkImageIOBase.h.  The patch (against CVS head) is attached.
>
> I would propose to commit this, but not until I get the go-ahead from
> someone at Kitware.  I'd appreciate other developers looking this over
> for accuracy and style.
>
> You'll notice two "TODO: Deprecate?" comments.  I don't propose to
> commit these.  However, neither WriteImageInformation() nor
> m_Initialized can reliably be used in the code base today.  So what
> should one do about them?
>
> Any comments welcome.
>
> Thanks,
> -Steve
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iD8DBQFJXrCQ0i2bPSHbMcURAl8+AJ9zP4FyhOmqVGww9g5+MZdf+v/85QCfcfxQ
> YY625aOQ4usBrNadH/eDTzQ=
> =W+CD
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Insight-developers mailing list
> Insight-developers at itk.org
> http://www.itk.org/mailman/listinfo/insight-developers
>
>