Cart
[Home] [By Thread] [By Date] [Recent Entries]
Re apps placing requirements on preserving attribute order: > That's fine if the > application totally controls the data format all the way down to the > character level, and is using XML for some reason that doesn't involve data > interchange (for example, simply to avoid having to write a parser for some > internal file format). And instead, they're writing a parser for this strange dialect of XML? Why not use "real XML" rather than such an application-specific dialect? Or are they instead writing code to depend on a behavior of some particular XML parser that's likely not to be shared by other parsers? The developer in question might be trying to wedge vendor-specific requirements into an architecture. If not the intent, that's the result. Bad idea IMO. - Dave
|
