Topic
Software portability
About: Software portability is a research topic. Over the lifetime, 8987 publications have been published within this topic receiving 164922 citations. The topic is also known as: portability.
Papers published on a yearly basis
Papers
More filters
TL;DR: The method of transferring the BCPL compiler is described including the specification of OCODE which is the language used as an interface between the machine independent and machine dependent parts of the compiler.
Abstract: Methods of achieving program portability are discussed, with particular reference to the mobility of compilers. The method of transferring the BCPL compiler is then described including the specification of OCODE which is the language used as an interface between the machine independent and machine dependent parts of the compiler.
71 citations
Patent•
10 Dec 1999
TL;DR: In this article, a system and method for providing portability of internet addressing maintains additional IP addressing information in number portability databases located throughout provider domains in a telecommunications network, in conjunction with additional Number Portability Request messaging information.
Abstract: A system and method for providing portability of internet addressing maintains additional IP addressing information in number portability databases located throughout provider domains in a telecommunications network. This additional IP addressing information, in conjunction with additional Number Portability Request messaging information, permits portability of addresses across telecommunication and data communication networks in a transparent fashion.
71 citations
TL;DR: The object-oriented Robot Independent Programming Environment (RIPE), which is being used for the rapid design and implementation of a variety of applications, is described, and workcell tasks demonstrating robot cask handling operations for nuclear waste facilities, which are successfully implemented using this object- oriented software environment are discussed.
Abstract: The object-oriented Robot Independent Programming Environment (RIPE), which is being used for the rapid design and implementation of a variety of applications, is described. A system architecture based on hierarchies of distributed multiprocessors provides the computing platform for a layered programming structure that models the application as a set of software objects. These objects are designed to support model-based automated planning and programming, real-time sensor-based activity, error handling, and robust communication. The object-oriented paradigm provides mechanisms such as inheritance and polymorphism which allow the implementation of the system to satisfy the goals of software reusability, extensibility, reliability, and portability. Designing a hierarchy of generic parent classes and device-specific subclasses which inherit the same interface allows a Robot Independent Programming Language (RIPL) to be realized. Workcell tasks demonstrating robot cask handling operations for nuclear waste facilities, which are successfully implemented using this object-oriented software environment, are discussed. >
71 citations
TL;DR: This paper addresses a set of capabilities required of a container orchestration platform to embody the design principles as illustrated by twelve factor app design and provides a non-exhaustive and prescriptive guide to identifying and implementing key mechanisms required in a container Orchestration platform.
Abstract: As compute evolves from bare metal to virtualized environments to containers towards serverless, the efficiency gains have enabled a wide variety of use cases. Organizations have used containers to run long running services, batch processing at scale, control planes, Internet of Things, and Artificial Intelligence workloads. Further, methodologies for software as a service, such as twelve-factor app, emphasize a clean contract with the underlying operating system and maximum portability between execution environments.1 In this paper, we address a set of capabilities required of a container orchestration platform to embody the design principles as illustrated by twelve factor app design. This paper also provides a non-exhaustive and prescriptive guide to identifying and implementing key mechanisms required in a container orchestration platform. We will cover capabilities such as cluster state management and scheduling, high availability and fault tolerance, security, networking, service discovery, continuous deployment, monitoring, and governance.
71 citations
TL;DR: The SLATEC Common Mathematical Subroutine Library is an experiment in resource sharing by the computing departments of several Department of Energy Laboratories to cooperatively assemble and install at each site a mathematical subroutine library characterized by portability, good numerical technology, good documentation, robustness, and quality assurance.
Abstract: The SLATEC Common Mathematical Subroutine Library is an experiment in resource sharing by the computing departments of several Department of Energy Laboratories. The objective is to cooperatively assemble and install at each site a mathematical subroutine library characterized by portability, good numerical technology, good documentation, robustness, and quality assurance. The result is a portable Fortran mathematical subroutine library of over 130,000 lines of code.Much of the following report is based on [1], a chapter to be included in a forthcoming book about mathematical software.
71 citations