Abstract: A conveyor system includes a frame, a drive roller carried by the frame, and a tail roller carried by the frame. The drive roller and the tail roller each include a relief channel positioned around a roller circumference. The conveyor system further includes a first intermediate roller positioned between the drive roller and the tail roller and carried by the frame, where the first intermediate roller has a channel positioned around a first intermediate roller circumference. The conveyor system also includes a continuous flexible belt positioned around the drive roller and the tail roller, where the continuous flexible belt has an exterior surface, an interior surface, and a guide extending inwards from the interior surface. The guide is positioned within the channel of the first intermediate roller and the guide is spaced apart from the drive roller relief channel and the tail roller relief channel.

Abstract: Annotation of exception information in a computer program. This annotation is not present in the source code itself, but is annotated during the compilation process or perhaps for purpose of analyzing the code. To perform the annotation, environmental rules are accessed regarding the environment in which the program is to be executed. The program is then evaluated in the context of these environmental rules to detect portions that, in the context of the environmental rules, may cause exceptions to be thrown. Those portions may then be annotated with exception information that describes any exceptions that could be thrown at that detected portion.

Abstract: A software development architecture is provided for constructing a wide range of software development tools. A software development tool can be created by integrating a specification specifying functionality specific to a set of software development scenarios into a software development scenario-independent framework. The integrated specification can then be compiled to create the software development tool. Alternatively, integration can be achieved at runtime without access to source code. The architecture can use any combination of the following: a software scenario independent intermediate representation format, one or more exception handling models capable of supporting a plurality of programming language specific exception handling models, a type system capable of representing the type representations of a plurality of source languages, and a code generator capable of generating code targeted for a plurality of execution architectures.

Abstract: Annotation of exception information in a computer program. This annotation is not present in the source code itself, but is annotated during the compilation process or perhaps for purpose of analyzing the code. To perform the annotation, environmental rules are accessed regarding the environment in which the program is to be executed. The program is then evaluated in the context of these environmental rules to detect portions that, in the context of the environmental rules, may cause exceptions to be thrown. Those portions may then be annotated with exception information that describes any exceptions that could be thrown at that detected portion.

Abstract: Methods and systems are described herein for extending configuration dependent extensible software programs. Classes of a core extensible software program may be extended by adding a configuration dependent extension. The extensions may be added statically prior to compiling the core version of a software program or dynamically at runtime. The declaration of extensible core classes may include an extensibility attribute with an indication of whether the class is statically extensible or dynamically extensible. An object description language is also described herein for appropriately declaring configuration dependent extensible classes. Also, a pre-processor is described herein for processing the object description language to generate a source code representation of the extensible class declarations and their extensions. The source code representation may then be used to generate the extended version of the core software program.

Abstract: Various intermediate representation techniques for software development tool scenarios are described. An intermediate representation format can be used for both high level and low level representations. The intermediate representation can be built from various operands and instructions types. Various annotations can be added to the intermediate representation without modifying its format. For example, flow control and data control can be explicitly represented by threading a graph through the intermediate representation.

Abstract: Various intermediate representation techniques for software development tool scenarios are described. An intermediate representation format can be used for both high level and low level representations. The intermediate representation can be built from various operands and instructions types. Various annotations can be added to the intermediate representation without modifying its format. For example, flow control and data control can be explicitly represented by threading a graph through the intermediate representation.

Abstract: A software development architecture is provided for constructing a wide range of software development tools. A software development tool can be created by integrating a specification specifying functionality specific to a set of software development scenarios into a software development scenario-independent framework. The integrated specification can then be compiled to create the software development tool. Alternatively, integration can be achieved at runtime without access to source code. The architecture can use any combination of the following: a software scenario independent intermediate representation format, one or more exception handling models capable of supporting a plurality of programming language specific exception handling models, a type system capable of representing the type representations of a plurality of source languages, and a code generator capable of generating code targeted for a plurality of execution architectures.

Abstract: Improved weakest condition analysis. In one embodiment, a computer-implemented method including first identifying a set of candidates of a computer program that are potentially defective, via a predetermined data flow analysis. In one embodiment, the predetermined data flow analysis may be a static single assignment analysis, or a partial redundancy analysis. Next, each of these candidates is examine via a weakest precondition analysis to determine whether the candidate actually is defective. The end result is a faster analysis, because the weakest precondition analysis is only performed on those candidates that are deemed potentially defective by the initial predetermined data flow analysis performed.

Abstract: A conveyor apparatus for transporting items via an endless conveyor belt having at least one locking member. At least one interchangeable holder element is adapted to releasably interlock with the locking member provided on the conveyor belt, with the locking member exerting a downward force on the holder element when tension is applied to the belt in use. As a result, the holder element is preloaded against the outer surface of the belt. The preload is at least partially decreased when traveling in an arcuate path about the end pulleys of the conveyor system. Accordingly, the holder elements may easily be removed and replaced without adjusting the tension of the conveyor belt.

Abstract: A conveyor system comprises a pulley provided with a bearing. The bearing includes an outer bearing race with an outer surface. The conveyor system further comprises a frame with a side plate having a top end defining a first cut-out. At least a portion of the outer surface of the outer bearing race is engaged with the first cut-out. The side plate also defines a second cut-out providing an opening into the first cut-out. The second cut-out facilitates insertion of the bearing into the first cut-out.