HP3000-L Archives

June 1998, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Gopalakrishnan M <[log in to unmask]>
Reply To:
Gopalakrishnan M <[log in to unmask]>
Date:
Tue, 9 Jun 1998 18:09:11 +0530
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
Hi John,

  As you might know calendars in different countries changed at different
  times around the year 1752 and our date intrinsics ignores this fact.
  So, after this particular date change, date intrinsics should work
  properly (for example, you should get consistent and correct date
  manipulation at least from 01-01-1753).

  You should not be having any problem with dates starting 01-01-1753
  (and if you found anything then it is a bug, please submit a service
  request).

regards

Gopi

John J Archer wrote:
>
> I response to a question from Greg Stigers (see below) on this discovery,
>
> The date range is ok for the Gregorian dates 01/01/1601 thru 01/24/1601
> but not for Julian dates 1601-001 thru 1601-024. I'm not concerned about
> dates before that because the Cobol date functions don't work below that
> date '01-01-1601'. I want to establish the minimum date value for my
> utility and I'm concerned that if the intrinsics have problems here then
> what about a date that is current or future?
> Thanks,
> John
>
> John J. Archer         (MY VIEWS, NOT MY EMPLOYER'S)
> ph:(330) 798-2190      IBM Global Services (for General Tire)
> fx:(330) 798-3912      One General St. Akron, Oh. 44329
> E-Mail: john [log in to unmask]

--
Gopi (M Gopalakrishnan)                               [log in to unmask]
Hewlett Packard India Software Operations

ATOM RSS1 RSS2