Paul Cadach wrote: > Don't forget about my ticket which splits huge say.c into many small > language-dependent pieces and provides common interface to support different > languages. Also, next step was planned is to move some language-specific stuff > into it like replace channel's "char *lang" variable with pointer to language > structure to not perform many string comparsions each time.
I think it sounds like Paul and Luigi have good, but differing, ideas on the best way to handle this. I also see no need to make any 'interim' steps; we are still in 1.4 'architectural change' mode until the end of this month, so let's get this figured out. I think it does make quite a bit of sense to make the approach table-driven as Luigi has proposed, but we need to ensure that we don't lose the ability to handle the complexities of languages with unusual ways of speaking numbers, dates and times. Using C code allows for that, but at a cost. (Also, I'm happy to see these discussions moved back to this list... Mantis is _not_ a good place for architectural or design discussions at all). _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
