Difference between revisions of "Studio:How does STRIDE know about my APIs and messaging interfaces?"
m (Text replace - 'Category:SCL' to 'Category:Studio:SCL') |
|||
| Line 1: | Line 1: | ||
STRIDE learns about APIs and messaging interfaces through the header files of embedded applications. To clarify ambiguities in complex interfaces, developers add pragma statements (SCL) to further specify the characteristics of interfaces and data types. STRIDE compiles through these header files and builds an XML database of the application interface signatures. These application interfaces are now remotely available to the developer through STRIDE. | STRIDE learns about APIs and messaging interfaces through the header files of embedded applications. To clarify ambiguities in complex interfaces, developers add pragma statements (SCL) to further specify the characteristics of interfaces and data types. STRIDE compiles through these header files and builds an XML database of the application interface signatures. These application interfaces are now remotely available to the developer through STRIDE. | ||
| − | [[Category:SCL]] | + | [[Category:Studio:SCL]] |
Latest revision as of 10:13, 21 August 2009
STRIDE learns about APIs and messaging interfaces through the header files of embedded applications. To clarify ambiguities in complex interfaces, developers add pragma statements (SCL) to further specify the characteristics of interfaces and data types. STRIDE compiles through these header files and builds an XML database of the application interface signatures. These application interfaces are now remotely available to the developer through STRIDE.
