Main > Software Forum
NO MORE LISTINFO in 84!
Silver:
argh! I ditched my xml code as it was so slow at parsing the xml (although partly cos I'm not that hot at coding either....)
might have to look at parsing the xml as a txt file as all the info will be there, just in a different format/location.
Sigh. ;-)
Minwah:
Well at least usually the games list only has to be generated once per MAME version...
Howard_Casto:
Xml blows! I don't know why everyone jumped on the xml bandwagon.
Sure it's easy to parse..... if your using an "internet" based langauge. Everything else needs a custom routine wrote. And as there is only one fe wrote in java, the rest of us are pretty much screwed.
Also xml wastes space...... those hierarchial groupings in ascii text take up a lot more space than simply typing it. (Which is what the listinfo does.) For anyone using vb and some of the other visual studio languages this is a nightmare as anything ascii reads slow into memory.
Long story short.... as usual mame devs are completely out of touch with fe developers. When listinfo first came out we complained the format was illogical and hard to parse... I guess their "solution" was to convert the whole mess to xml, which merely adds another step to the process instead of simplifying it.
Daniel270:
So which Frontends are now compliant with Mame .84?
Minwah:
--- Quote from: Daniel270 on July 02, 2004, 11:30:46 pm ---So which Frontends are now compliant with Mame .84?
--- End quote ---
Not sure exactly...if I understand SirP correctly, MAMEWAH should still work if you use a DAT File List Generation Method, and create a datfile from using 'mame -listxml|xml2info > mame.dat'.