Get desktop application:
View/edit binary Protocol Buffers messages
* Placeholder until I figure out how to import properly
Used in: , , , ,
(message has no fields)
* Used to communicate results of analysis / checking passes. Limited to Block and Link objects.
Used in:
free-form error message
full traceback TODO: should there be a structured stack trace?
source locator, eg line of failing constraint
* Arbitrary metadata stored in tree form.
Used in: , , , , , , , , , , , , , , , , , ,
* An unknown type just means we don't have some specific expected structure. A known type is shorthand to tell us what fields we should expect and how to decode the stored data. None of this is enforced anywhere, so programmer beware, getting the type and other information right is your job.
* I wanted to split binary and text data, since we might just want to dump a raw file/image/datasheet in here for safekeeping. Mixing up binary and textual formats is just a recipe for trouble.
Defined formats Note: key should be the message definition name (eg, SourceLocator) TODO: how to handle multiple metadata of a given type?
Used in:
* For locating source data
Used in: ,
package name (portable, not tied to an absolute path) that locates the file
line number
character offset within the line
Used in:
source defining this class, would be present in library
source of instantiation, would be present in design