[Insight-developers] Interface Mismatch !

[Stephen R. Aylward]

Hi,

An "acceptable" option is to have both functions in both classes.   This 
makes the interfaces compatible and doesn't break existing code.

We could then also add a warning to one of those functions (in both 
classes) to indicate that it will be deprecated in a future version.  I 
think we should put that warning in the Rotate3D function - it is not 
consistent with the ITK API.

Stephen

Ashish Poddar wrote:
> Hi,
>  I know this can break quite a lot of existing code, but nevertheless, I 
> think this can be thought about !
>  The interface for VersorTransform is having a function - SetRotation with 
> same semantics as the Rotate3D function of CenteredAffineTransform and hence 
> I suggest renaming one of them to match the other.
>  regards,
> Ashish.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Insight-developers mailing list
> Insight-developers at itk.org
> http://www.itk.org/mailman/listinfo/insight-developers

-- 
===========================================================
Dr. Stephen R. Aylward
Associate Professor of Radiology
Adjunct Associate Professor of Computer Science and Surgery
http://caddlab.rad.unc.edu
aylward at unc.edu
(919) 966-9695