Search

The article provides information on the Common Language Infrastructure (C++/CLI). C++/CLI can be defined as an extension of the C++ programming language that provides features such as properties, events, garbage collection and generics for all types. In this article, the author examines C++ programs that are minimally ported to the new environment using managed extensions. The purpose is to determine whether the programs are susceptible to the buffer overflow vulnerabilities that have plagued C and C++ programs. The compiler generates Microsoft Intermediate Language when using managed extensions.

Provides information on the garbage collection capability of Java program language. Special cases where memory management must be handled by the application; Description of object pooling; Web applications of caching and pooling; Design aspects the caching and pooling shares; Description of writing memory-management code.

Presents information on a study which described the use of garbage pooling in reducing the number of garbage collection executions in a Java application. Advantages and disadvantages of C++ garbage-collected approaches; Execution time of the garbage collector; Information on the ObjectPool class; Conclusions.

Examines several incremental memory-management algorithms. Reference counting algorithm; Practical concerns for a performance-oriented C/C++ collector; Factors that posed challenges for any allocator.

Discusses the advantages of using the Java computer programming language to leaks in computer memory. Dynamics of memory management in Java; Myths about garbage collection in Java; Conclusion.

This article focuses on the BuDDy library that allows the implementation and manipulation of Boolean expressions. The library exposes a Binary Decision Diagram interface rather than a Boolean expression interface. BuDDy is implemented in C but has a wrapping C++ interface. It has an internal garbage collection mechanism optimizing its memory usage, totally transparent if one decides to use the C++ interface. BuDDy also has a cache that saves the last results of operations. Almost everything performance related is configurable through the interface, and the library begins running with default values, so one can start using it without being familiar with all the possible configurations. BuDDy has a rich set of operations, which can help implement very complex operations with only a few code lines. Among the operations in the interface are the abilities to define the variables of the expressions one is going to create, refer a large vector of binary variables as a vector of encoded integers and create a vector of expressions. The manipulation operation includes the ability to perform various kinds of Boolean operations on one or more expressions and vector-oriented operations on vectors of expression, referring to them as encoded integer.

The article discusses the WebLogic RealTime (WLRT) 1.1, a new software solution developed by BEA Systems Inc. WLRT is composed of an optimized WebLogic application server and the JRockit Java Virtual Machine, and it supports applications that demand fast, predictable response times and low latency. It lessen the latency brought by garbage collection and provides better performance regardless of whether the application is Java or JavaEE executing in a third-party container. Moreover, WLRT is designed to help the developers and information technology (IT) administrators meet the needs of mission critical enterprise Java deployments, increase productivity and reduce IT project costs.

The article highlights the topics discussed during the 2004 ISO C++ Standards meeting in Redmond, Washington from October 17 to 22. The final technical changes were voted into the Library extensions technical report, and this batch of extensions to the C++ Standard Library has been completed. This batch of extensions includes support for pointers, hash-based containers, type traits, random number generators, expressions, tuple types, a function wrapper and a slew of mathematical functions. The Evolution Working Group has worked through proposals. Here are some of the proposals that are likely to come up for vote. These are the C99 long long, fixing right angle brackets, a static assert facility for compile-time assertions, nullptr as a spelling for the null pointer value, enumerations, extended friend support and adopting C99 preprocessor extensions. The Evolution Working Group was organized into three groups. First, support for library building. This will focus on areas pertinent to building libraries in C++, including better support for generic programming. Second, modularity and libraries. This will focus on standardizing support for libraries and to provide a module system in C++. Third, safety, regularity and performance which focus on issues including security, threading and garbage collection. Under the Library Working Group, support for novices and incidental programmers was initiated. This area concentrates on providing simplification via libraries.

The article focuses on the JSR-001 Real Time Java Specification standard that addresses any real-time configuration. This standard includes various types of scheduling for the restricted use of memory that allows the elimination of the garbage collector for time-critical, hard real-time applications. Garbage collection support can address hard real-time applications. Mechanisms have been developed to allow Java applications to be bolted together.

Discusses the impact of Java virtual machines on the simplistic garbage collection. Consideration of Java for embedded applications; Lack of available memory for Java applications; Use of techniques in hybrid garbage collector.

Explores NewMonics Inc.'s hybrid real-time garbage collection (GC) approach for embedded Java. Combination of a copying generational (GC) with a conventional mark-and-sweep GC; Advantages and disadvantages of hybrid GC; Approach of hybrid GC.

Focuses on memory leak, a gradual deterioration of system performance that occurs over time as the result of the fragmentation of a computer's random-access memory (RAM) due to poorly designed applications that fail to free up memory segments when they are no longer needed. Details on garbage collection; How a memory leak occur in a system; Program development tools that provide automatic housekeeping.