Gabriel Sechan wrote: > In 99% of apps, internationalization is overkill. Unless a human is > meant to be editing the file (such as a config file), its just a waste > of CPU power and time.
Okay, that part I'd disagree with. Anytime you have strings as your data type, there is a distinct possibility you will need some kind of internationalization. It's not a given, but it applies to far more than 1% of the cases, and unfortunately people tend not to realize that. >> Third, XML parsers *complain* when you feed them garbage. If you >> don't get your formatting and nesting correct, most XML parsers are >> free to dump your crud into the bitbucket any way they please. > > Yup, because just dumping the doc rather than trying to route around the > problem is a great idea. Nah, I didn't really want all that data. So > whats a few missing bank transactions gonna cost anyway? Hehe, I've actually frequently had to write a "front end parser" that reads the document and performs corrections just so I can stuff it in to the "real" parser. How's that for efficient? ;-) --Chris -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
