Re: [tinyTiM-discuss] tinyTiM MIO vs. TMAPIX I/O

[Lars H. <he...@se...>]

Hi Markus,

>> I wonder if I should drop tinyTiM MIO in the near future.
>>   
> To make the decision process a bit more challenging: *-2*

:P

> -- That's what I'd love to say :p, but seriously, while I have yet to
> review/compare the individual TMAPIX interfaces, the more generic they
> are, the better. A short example how to migrate between the two
> libraries in question would be nice (and also an occasion to fill the
> wiki). :)

Yes, there will be documentation, of course. The main change will be
the package name, the interfaces / implementations are direct copies
from tinyTiM, so I don't expect that it causes any trouble to migrate.
IIRC you use semagia-mio directly and bypass tinytim-mio anyway,
right? Then you shouldn't recognize any change.

> For those who want to support both TMAPI 1.x and 2.x backends, this
> shouldn't change much anyway, right? (So, actually, my vote is +1)

I didn't test it with tinyTiM 1.5 / TMAPI 1, but it may work. You
can't use the TMAPIX writers, of course. They use the TMAPI 2.0
interfaces.

Best regards,
Lars
-- 
Semagia 
<http://www.semagia.com>