You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When svd2ada terminates with an error message, it would be extremely helpful to get a line number (referring to the *.svd file) to locate the root cause of the problem.
I think i proposed that before, as a side note in another issue.
Do you have a specific example of error message where such line information would have been useful?
I don't see such information that easy to provide in general, as the parsing of the xml file is performed in a first pass (that should generally not generate errors, supposing the svd file is valid), and then forgets completely about the DOM tree when actually processing the SVD data to generate the bindings.
When svd2ada terminates with an error message, it would be extremely helpful to get a line number (referring to the *.svd file) to locate the root cause of the problem.
I think i proposed that before, as a side note in another issue.
To me, http://docs.adacore.com/xmlada-docs/dom.html#adding-information-to-the-tree reads like it's possible to add line numbers even when using the DOM parser.
Have you already checked this possibility? You probably have the opportunity to get infos directly from the XML/Ada experts... 😉
The text was updated successfully, but these errors were encountered: