Platinum Technology, Inc.

Michael D Lips

A utility with which a programmer can generate or alter computer code for a calendaring function, and test the code prior to compilation. Entering the program in edit mode, the programmer locates a portion of the program where code for a calendaring function is to be generated or altered, and invokes the date logic generator. The date logic generator provides an initial window with a choice of calendaring functions, and upon selecting a calendaring function, a parameters window displaying a number of first-level parameters for that function is provided. Depending on the specification of the values of the first-level parameters, sub-windows with second-level parameters may be provided. And, in general, depending on the specification of the values of the n-level parameters, (n+1)-level parameters may be provided in sub-windows. The parameters provided at any instant are only those which have already been specified or those that require specification. When the programmer believes the calendaring function is correctly chosen and its parameter values correctly specified, the operation of the function may be tested by a testing utility without requiring compilation of the computer code. Data for the calendaring function is entered in a testing utility sub-window, and the programmer can compare the testing utility output with an expected output. If the testing utility output and the expected output differ the programmer can modify the function or the function parameter values as appropriate. Further runs of the testing utility and modifications of the parameters of the calendaring function can be performed as needed.

Date logic generator

Conversion of Gregorian calendar dates to dates of a 360-day-year calendar (i.e., a calendar having twelve months of 30 days each), and 360-day-year calendar dates to Gregorian calendar dates, are performed using a single three-column 367-entry conversion table. A search table unit searches the conversion table from the bottom upwards, i.e., a table search index is initialized to a value of 367, and decremented by unity each time a comparison is made and a match is not found. A first field in each row of the conversion table contains Gregorian leap year calendar days-of-the-year, a second field in each row contains Gregorian non-leap year calendar days-of-the-year, and a third field in each row contains 360-day-year calendar days-of-the-year. A graph of Gregorian days-of-the-year versus 360-day-year days-of-the-year has both vertical and horizontal sections. If a conversion from a Gregorian date stored in a month/day character register to a 360-day-year date is to be made, the field to be searched is dependent on the value of a flag is a leap year flag register. If a conversion from a 360-day-year date stored in a 360-day-year character register to a Gregorian date is to be made, after a match between the 360-day-year date and an entry in the third field is found the value of the flag in the leap year flag register determines which field the conversion day-of-the-year is taken from.

Date conversions with a 360-day-year calendar

A calendaring system which provides accurate calendaring of all dates between Jan. 01, 0001 and Dec. 31, 9999 by implementation of an extended set of leap-year rules. The system includes a variety of additional useful features including: multiple holiday tables; flexible date formats; free form definition of processing days; full support for fiscal calendaring units; changeable endpoint counting modes; and integrated support for the current date in date calendaring calculations.

Growing community of inventors

San Francisco, CA, United States of America

Michael D Lips