Qualitatively annotated code

• US 7,987,456 B2
• Filed: 01/24/2006
• Issued: 07/26/2011
• Est. Priority Date: 01/24/2006
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Mariani, Rico
• Primary Examiner(s): VU, TUAN A
• Application Number:
  US11/275,690
• Publication Number:
  US 20070180455A1
• Time in Patent Office: 2,009 Days
• Field of Search: 717101-103, 717106-108, 717/143, 707101-102, 709/220, 719/328, 715/714
• US Class Current: 717/143
• CPC Class Codes: G06F 8/73 Program documentation

Abstract

Data associated with at least one module of code may be annotated in such a manner as to provide guidance regarding usage of the module.

Claims

1. A method of utilizing qualitatively annotated code, comprising:

analyzing code to determine a functional intent of the code and associate an annotation with the code based on the functional intent of the code, wherein the functional intent is indicative of an intended use of the code and describes one or more contexts in which the code is appropriate for use rather than describing a precise function of the code;

the functional intent provided as an annotation file received into a runtime environment for processing the compiled code, the annotation file including one or more of a classification or persona to represent qualitative information on the intended use of the code;

compiling the code;

using a processor coupled to a system memory, receiving a catalytic action to affect compiled code;

in response to receiving the catalytic action, using the processor to read the compiled code and the associated annotation file to decipher the functional intent or other designated functional characteristics of the compiled code based on established criteria;

based on the deciphered functional intent or other designated functional characteristics of the compiled code, associating the classification with the compiled code, wherein the classification is at least one of;

inner-loop code that is likely to be called in a bigger loop by a client application, program, function or other assemblage of code, as part of a bigger algorithm,

throughput code that is likely to be used in a batch process or service process,

interactive code that is likely to be used by part of an application, program, function or other assemblage of code that is driven by interactive events, or

startup code that is likely to appear on a startup path for a corresponding application, program, function or other assemblage of code; and

displaying to a user in the runtime environment guidance based on the classification associated with the compiled code, the compiled code associated with an application programming interface (API) of the runtime environment, the guidance comprising;

for a classification of inner-loop code, advising that such code may be called by code that is assigned of a classification of throughput code, interactive code or startup code;

for a classification of throughput code, advising that throughput code is not functionally compatible with inner-loop code and therefore may not be called by inner-loop code;

for a classification of interactive code, advocating calling code that has been assigned an inner-loop classification;

for a classification of startup code, advising discouragement or denial of calls from code that has been assigned another classification;

wherein the programming guidance indicates at least one of;

whether the API is functionally compatible with a method that is calling the API;

whether a called method is functionally compatible with the API;

or

a method that may be successfully called by the API.