[
Lists Home |
Date Index |
Thread Index
]
> >
> > Have you seen the alternatives, like the .NET transformation
> > API with about 20 overloaded transform() methods?
>
> So given the choice of methods that take useless interfaces
> (since they
> have to cast to get anything useful) and APIs with lots of overloaded
> methods that support a rich set of data sources, why would
> you think the
> former is better?
(a) it's more extensible, and (b) it's more memorable for the user.
Michael Kay
http://www.saxonica.com/
|