Abstract: Concurrency within a loop construct is enabled by introducing state variables and State Variable Mutation principles on these state variables in the loop construct. The loop construct is associated with variable(s) called State(s) or State variable(s). These state variables are the ones that are mutated within an associated loop construct. Access to these states outside this loop construct is not permitted. State Variable Mutation Principles are the set of rules defined for mutating these state variables. These rules are in place to aid optimization, such as concurrent execution of state modifications within the loop construct. Rules are handled by a Loop Concurrency Validator introduced in a compilation process. Rules imposed on the state variables along with the delayed write followed within the loop construct enables instructions within the loop construct to be executed in parallel.

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: 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 CANDIDATE tag conveys a request to a compiler to identify multiple candidate constructs, compile each set of candidates or sets of multiple candidates into executables, and profile the compiled executables. Results of the profiling can be compared and a best candidate or set of candidates selected based on one or more of various criteria. A CANDIDATE tag may incorporate properties, permissions, and generate notifications. 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 FIX or OPTIMIZE tag identifies a construct to be altered. An ALTERNATE tag identifies an alternate construct to be compiled while ignoring a FIX or OPTIMIZE tagged construct of the same name. The alternate construct may be marked for ignoring once the other tagged construct of the name is fixed or optimized. Each tag may incorporate properties, permissions, and generate notifications. 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 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.

Abstract: Extension of built-in object management functions such as create, update, and delete are illustrated. The developer can extend any of these functions for management of objects for a type within its type definition in source code. In one aspect, an object management function is extended to accept one or more additional arguments to capture one or more parameters, stored as metadata associated with the object, and accessible for use with further object management as well as other functions. In another aspect, one or more constraints are defined to implement control over management of an object of the extended type. At runtime, a constraint is evaluated, and, when the constraint evaluates to a predefined value, the object management function is prevented from completing.

Abstract: A system and method for mapping and transforming email messages to communication stream messages are described. An email message is processed by a mapping engine which extracts elements of the email message, maps and transforms the extracted elements of the email message to a communication stream message to be presented via a communication stream system.

Abstract: A programming language and compiler support inheritance and type extensions. Program code defines user-defined independent and dependent-link data types. Elements of an independent data type can be inherited by a dependent-link data type that can extend the scope of the independent data type and the scope of one or more elements of the independent data type. Data types and type extensions are instantiated in memory as uniquely identified objects that reference one another in a manner that controls inter-object access.

Abstract: A system and method for mapping and transforming communication stream messages to email messages are described. A communication stream message is communicated to a mapping engine which extracts elements of the communication stream message, maps and transforms the extracted elements of the communication stream message to an email message to be presented via an email system.

Abstract: A system and method for mapping and transforming communication stream messages to email messages are described. A communication stream message is communicated to a mapping engine which extracts elements of the communication stream message, maps and transforms the extracted elements of the communication stream message to an email message to be presented via an email system.

Abstract: A document editing system using a third party application having an embedded document editing module is disclosed. The system includes a client-side document editing engine that accepts requests to edit a document from and displays at least a portion of the document to a user of the client-side system. The system includes a first server-side application engine that processes the requests to edit the document. The system can include a second server-side data storage engine that stores the document in a remote storage location.

Abstract: A document editing system using a third party application having an embedded document editing module is disclosed. The system includes a client-side document editing engine that accepts requests to edit a document from and displays at least a portion of the document to a user of the client-side system. The system includes a first server-side application engine that processes the requests to edit the document. The system can include a second server-side data storage engine that stores the document in a remote storage location.

Abstract: A messaging system supports a presentation session with participants of the presentation, a presenter and one or more audience members. The message system allows the participants to share messages and documents via respective client/mobile devices. An application on each mobile device allows the audience member to peruse and comment on document portions (e.g., pages, images, or slides) being presented. The presentation sequence for the document portions can be managed by the presenter, or document perusal can be decoupled from the presentation sequence to allow audience members to focus on past or future document portions. Comments of the audience member or other participants can be linked to corresponding document portions. A user may repeat, reprise or continue a past presentation.

Abstract: A system and method for creating a document in a messaging environment is described. A communication including a document specification including zero or more formatting commands and content is received from a sender and processed. The system and method determine whether the document specification is in a done condition, and iterates until done. A formatted document is also created and returned to the sender and recipients.

Abstract: A system and method for creating, managing, and using an application in a messaging environment is described. A communication including an application specification comprising zero or more commands is received from a sender and processed. The system and method determine whether the application specification is in a done condition, and iterates until done. A confirming specification, including revisions made while iterating, is also created and returned to the sender and recipients.

Abstract: A system and method for communicating a multimedia presentation between a presenter and an audience is described. Services provided via a network facilitate the communication, and include real-time determination of remaining portions of a presentation responsive to “on the fly” presentation modifications, automated filtering and prioritization of audience feedback to a presenter, integration with one or more customer data resources, and repositioning of a shared electronic pointer by reorienting a wireless handheld presenter device.