Open implementation of the Record JAR / News: Recent posts

Open-RJ is an Open Source C Structure File Reader library for the Record-JAR format. It can read Record-JAR databases from files or from memory.

Open-RJ is highly efficient, involving only two memory allocations to read an entire Record-JAR database file.

Open-RJ is written in portable C, and provides mappings to C++ ('classic' C++ and STL), Ch, COM, Java, .NET, Python and Ruby.

Open-RJ is completely free and includes source released under a BSD-style licence. ... read more

see release notes for details

Summary:

1. Open-RJ/C++.NET:
~ Corrected bug in Database class, whereby the Fields property actually
returned a collection of Record instances, rather than Field instances.
+ new single-parameter constructor for FileDatabase, which assumes
ElideBlankRecords
+ new single-parameter constructor for MemoryDatabase, which assumes
ElideBlankRecords
+ Record.GetFieldValue() method overloads

2. Open-RJ/Ruby:
+ Database.records property
+ Database.fields property... read more

Summary:
1. New features: Field Name Aliasing and Case-insensitive Field Lookups.
2. Significant refactoring and enhancement of the Open-RJ/.NET mapping.
3. And 21 new C and C++ example programs.

Details:

This release contains new core library support for Field Name Aliasing and
Case-insensitive Field Lookups, which are reflected in the C++, STL, .NET,
Python and Ruby mappings. Also incorporated is a significant refactoring and
enhancement of the Open-RJ/.NET mapping, including new classes, methods,
properties and enumerations. And, finally, there are 21 new C and C++
example programs that distill Open-RJ programming knowledge of the core
library and C++ & STL mappings.

Two additions to the base API:

+ ORJ_FormatErrorA(), a rich error formatting function, providing sprintf()-like
semantics, with Open-RJ error and parse-error information retrieval

+ ORJ_Record_FindNextFieldA(), a flexible function for finding fields based on
field positions and/or names and/or values.

Minor update from 1.3.3, with facility to process \r\n on any platform