Abstract: A set of construct-modification tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. Tags may incorporate properties, permissions, and generate notifications. Example tags include IGNORE, DEACTIVATE, OPTIMIZE, FIX, ALTERNATE, PROTOTYPE, REQUESTREVIEW, REVIEWED, CANDIDATE, and BESTCANDIDATE. Methods ensure that tags no longer remain in source code once the software development process enters the production phase.

Abstract: Construct-modified tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. A REQUESTREVIEW tag conveys a request to a compiler to notify a reviewer that source code is ready for review. A REVIEWED tag indicates a review has been performed and may signify code acceptance. Alternatively, a FIX or OPTIMIZE tag may be used to identify further code development requirement. These tags may incorporate properties, permissions, and generate notifications. Methods may facilitate code review and feedback in other aspects. Methods ensure that tags no longer remain in source code once the software development process enters the production phase.

Abstract: A compile-time link type manager is defined to facilitate development of source code with disciplined link type object management at runtime. In one aspect, the link type manager ensures that all link type object management constructs have associated event handlers. Additionally, an event handler can be evaluated at compile time to ensure that it meets certain conditions for the particular link type, referred to as link-type criteria.

Abstract: Construct-modification tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. A hierarchy of developers and associated permissions is maintained. A tag may be associated with one or more developers as well as one or more permissions. Notifications associated with tags may be issued to one or more developers in response to a conveyed compiler request. General messages to all the developers and personalized messages to one or more developers indicate the presence of tags and need to resolve issues before the software development process enters the production phase.

Abstract: Construct-modification tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. A DEACTIVATE tag conveys a request to a compiler to deactivate an associated construct, as well as to find and deactivate dependencies of the construct. A DEACTIVATE tag may incorporate properties, permissions, and generate notifications, including a condition for evaluation, the deactivation conditionally responsive to the result of the condition evaluation. Methods ensure that tags no longer remain in source code once the software development process enters the production phase.

Abstract: Construct-modified tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. A REQUESTREVIEW tag conveys a request to a compiler to notify a reviewer that source code is ready for review. A REVIEWED tag indicates a review has been performed and may signify code acceptance. Alternatively, a FIX or OPTIMIZE tag may be used to identify further code development requirement. These tags may incorporate properties, permissions, and generate notifications. Methods may facilitate code review and feedback in other aspects. Methods ensure that tags no longer remain in source code once the software development process enters the production phase.

Abstract: A set of construct-modification tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. Tags may incorporate properties, permissions, and generate notifications. Example tags include IGNORE, DEACTIVATE, OPTIMIZE, FIX, ALTERNATE, PROTOTYPE, REQUESTREVIEW, REVIEWED, CANDIDATE, and BESTCANDIDATE. Methods ensure that tags no longer remain in source code once the software development process enters the production phase.

Abstract: Construct-modification tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. A hierarchy of developers and associated permissions is maintained. A tag may be associated with one or more developers as well as one or more permissions. Notifications associated with tags may be issued to one or more developers in response to a conveyed compiler request. General messages to all the developers and personalized messages to one or more developers indicate the presence of tags and need to resolve issues before the software development process enters the production phase.

Abstract: A compile-time link type manager is defined to facilitate development of source code with disciplined link type object management at run-time. In one aspect, when a compile-time link type manager encounters a link type object management construct in source code, it will emit code for a runtime object management engine that processes generic link type object management instructions at runtime. It will also compile type-specific instructions from the link type object management construct for accessing the generic instructions in the runtime object management engine for affecting a link type object at runtime. A runtime object management engine may perform various checks, referred to as link-type criteria, at runtime prior to executing a link type object management instruction. When defined link-type criteria are satisfied for a link type object management instruction for an object at runtime, the instruction is carried out.

Abstract: A compile-time link type manager is defined to facilitate development of source code with disciplined link type object management at runtime. In one aspect, the link type manager ensures that all link type object management constructs have associated event handlers. Additionally, an event handler can be evaluated at compile time to ensure that it meets certain conditions for the particular link type, referred to as link-type criteria.