Free definition of poor implementation software for linux

Procinfo NG is a ground-up rewrite of the procinfo program. Procinfo NGs goal is to make the code more readable (and reusable) and to restore broken functionality of the original program.
The original program was written for Linux 1.0, and updated through 2.2. This version is for 2.6.
Enhancements:
- Updates were made to match what some Linux distributions have done to procinfo-18.
- Support for MSI and XEN interrupts were added.
- Some non-x86 architectures are handled.
- Assorted bugs and 80-character console nonsense were fixed.

Objective Modula-2 programming language is a hybrid between Smalltalk and Modula-2 based on the object model and runtime of Objective-C.
The design is an example how native Cocoa/GNUstep support can be added to static imperative programming languages without implementing a bridge.
Objective Modula-2s scope encompasses the design of the Objective Modula-2 programming language and the implementation of a compiler to implement it. The initial compiler will generate Objective-C source code.
Enhancements:
- This code is used to verify ideas and concepts which come up in the course of defining the language.
- It is in an early stage, incomplete and subject to frequent changes.

IronPython is an implementation of Python running on Microsoft .NET / Mono. It supports an interactive interpreter with fully dynamic compilation.

IronPython is well integrated with the rest of the framework and makes all .NET libraries easily available to Python programmers.

Poor mans Financial Calculator project is a small financial and basic mathematical operations calculator applet.
The calculator registers work like the mythical HP-12C financial calculator, even the "n" rounding behaviour. The yellow fields also serve as operands for the arithmetic operations; for such ops, the blue field will show the result.
BEGIN button: If enabled, means that the first payment is made at the beginning of the period (important only for financial operations that involve PMT register)
FPC button: if enabled, Fractionary part of the Period ("n") will also be calculated using Compound interest; if disabled, fractionary part will use simple (linear) interest, which gives slightly higher interest values.
Enhancements:
- This release translates the code and messages to English and changes the license to the LGPL.

PAPI aims to provide the tool designer and application engineer with a consistent interface and methodology for use of the performance counter hardware found in most major microprocessors.
PAPI enables software engineers to see, in near real time, the relation between software performance and processor events.
The Performance API (PAPI) project specifies a standard application programming interface (API) for accessing hardware performance counters available on most modern microprocessors.
These counters exist as a small set of registers that count Events, occurrences of specific signals related to the processors function. Monitoring these events facilitates correlation between the structure of source/object code and the efficiency of the mapping of that code to the underlying architecture.
This correlation has a variety of uses in performance analysis including hand tuning, compiler optimization, debugging, benchmarking, monitoring and performance modeling. In addition, it is hoped that this information will prove useful in the development of new compilation technology as well as in steering architectural development towards alleviating commonly occurring bottlenecks in high performance computing.
PAPI provides two interfaces to the underlying counter hardware; a simple, high level interface for the acquisition of simple measurements and a fully programmable, low level interface directed towards users with more sophisticated needs.
The low level PAPI interface deals with hardware events in groups called EventSets. EventSets reflect how the counters are most frequently used, such as taking simultaneous measurements of different hardware events and relating them to one another.
For example, relating cycles to memory references or flops to level 1 cache misses can indicate poor locality and memory management. In addition, EventSets allow a highly efficient implementation which translates to more detailed and accurate measurements.
EventSets are fully programmable and have features such as guaranteed thread safety, writing of counter values, multiplexing and notification on threshold crossing, as well as processor specific features. The high level interface simply provides the ability to start, stop and read specific events, one at a time.
PAPI provides portability across different platforms. It uses the same routines with similar argument lists to control and access the counters for every architecture. As part of PAPI, we have predefined a set of events that we feel represents the lowest common denominator of every good counter implementation.
Our intent is that the same source code will count similar and possibly comparable events when run on different platforms. If the programmer chooses to use this set of standardized events, then the source code need not be changed and only a fresh compilation and link is necessary. However, should the developer wish to access machine specific events, the low level API provides access to all available events and counting modes.
If an event or feature does not exist on the current platform, PAPI returns an appropriate error code. This significantly reduces the porting effort of code using PAPI because the semantics of each call to PAPI remains the same, just the argument lists need updating. In addition to the standard set, each PAPI implementation supports all native events through the ability to directly accept platform specific counter numbers. Definitions for most, if not all of these, are included as conditional macros in the header file. In this way, PAPI avoids having inefficient code to translate all events for all platforms into a uniform representation and back again.
This translation is only done for the relatively few events defined in the standardized set. Some processors like those in the POWER series have counter groups. They enable access to specific groups of counters, instead of individual events. This presents a serious portability problem, thus PAPI abstracts hardware counters from their groups with a packed naming scheme. Each counter control value or event is made up of the counter group number and the number of the specific counter in that group.
PAPI can be divided into two layers of software. The upper layer consists of the API and machine independent support functions. The lower layer defines and exports a machine independent interface to machine dependent functions and data structures. These functions access the substrate, which may consist of the operating system, a kernel extension or assembly functions to directly access the processors registers.
PAPI tries to use the most efficient and flexible of the three, depending on what is available. Naturally, the functionality of the upper layers heavily depends on that provided by the substrate. In cases where the substrates do not provide highly desirable features, PAPI attempts to emulate them as described below.
PAPI makes sure the underlying operating system or library guards against overflow of counter values.
Each counter can potentially be incremented multiple times in a single clock cycle. This combined with increasing clock speeds and the small precision of some of the physical counters means that overflow is likely to occur.
One of the more advanced features of PAPI is to provide a portable implementation of asynchronous notification when counters exceed a user specified value.
This functionality provides the basis for PAPIs SVR4 compatible profiling calls, that generate an accurate histogram of performance interrupts based on hardware metrics, not on time. Such functionality provides the basis for all line level performance analysis software, from the antiquated days of AT&Ts prof to SGIs SpeedShop. Thus for any architecture with even the most rudimentary access to hardware performance counters, PAPI provides the foundation for a truly portable, source level, performance analysis tool based on real processor statistics.
Enhancements:
- The API was extended to decouple abstraction layers from hardware support and to provide initial support for different types of performance counters.

SimpleJTA implements a standalone JTA compliant Transaction Manager. SimpleJTA project is primarily designed to be used when a J2EE server is not available, for example, in Servlet applications, or standalone Java programs.
SimpleJTA is being developed and tested with Oracle 9i and Apache Derby database management systems. It is fairly easy to add support for other database systems that support the XA interface.
Main features:
- SimpleJTA does not require a J2EE or Servlet container. It provides an implementation of UserTransaction interface so that an application using SimpleJTA can easily switch to another JTA implementation.
- SimpleJTA implements a transaction log to enable recovery after system crashes.
- Distributed transaction propagation between multiple application servers is not supported. There is no support for JTS.
- SimpleJTA implements the UserTransaction, Transaction and TransactionManager interfaces. The Transaction and TransactionManager interfaces have not been tested extensively.
- SimpleJTA provides its own JDBC datasources for Oracle and Derby. It is easy to add support for other database systems.
- SimpleJTA JDBC datasources and UserTransaction implementation can be registered to JNDI, but this has not been tested yet.
- There is experimental support for two JMS providers - Websphere MQ and Oracle AQ.
- SimpleJTA can be used within a Spring Framework managed application.
Enhancements:
- Added spring-dao to the list of dependencies in pom.xml.
- Added TransactionManager interface to SimpleUserTransaction.
- Added SpringTransactionManager bean definition to testConfig.xml.
- Fixed problems reported by FindBugs (4 defects remaining).
- Added very basic test case for ActiveMQ.
- Fixed incorrect classname in ActiveMQJMSConnectionFactoryAdaptor.

libCoroutine is a simple stackfull coroutine implementation, largely based on ucontext and fibers.

This library is built from the coroutine implementation of the Io programming language project.