Navigation  without Java Scripts

Visual Prolog 5.0 and Year 2000 Compliance

The Year 2000 ("y2k") problem (popular called the "Millennium Bug") arises from the use of a two-digit field to identify years in computer programs (for example 85 = 1985), and the assumption of a single century -- the 1900s. Any software so created will read (or attempt to read) e.g. "00" as the year 1900. Programs that use dates will fail or malfunction if these errors are not corrected.

Visual Prolog 5.0 introduces - as far as PDC knows - no problems with regard to the Year 2000 problem. The only date-related functions in the core language allow for setting and reading the current date from or to the underlying operating system, and thus, with respect to these functions, you should verify the Year 2000 compliance of the underlying operating system. The Visual Prolog programming language defines no particular representation for storing dates within an application, therefore, we can make no specific warranties about the year-2000 compliance of applications developed in Visual Prolog, since these will be year 2000 compliant or not, depending on date representation and data-handling choices made by the application programmer.

Note that both the underlying operating system and the computer where the program is running can also cause problems. We recommend that all Applications be carefully tested to see how they behave around and after the millennium change.