HP3000-L Archives

January 1997, Week 4

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:
M Gopalakrishnan <[log in to unmask]>
Reply To:
M Gopalakrishnan <[log in to unmask]>
Date:
Fri, 24 Jan 1997 13:47:12 +0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
Hi Duane,

>My previous response was too quick to assume I was in error. Not all the
>NL intrinsics accept a calendar date as you say!

 You are right Duane. I stand corrected. Thank you.

>One of them returns the calendar date (NLCONVCUSTDATE)! It is this NL
>intrinsic which now assumes that a date of 01/01/00 is in the year 2000
>instead of 1900 and will return a year of 100 instead of 0 encoded into
>the returned calendar date.

>So, I stand by my original comment:

>If you have code that wants to build a calendar date using NLCONVCUSTDATE
>you cannot do this for 1900-1949.

 Small correction:

  If you have code that wants to build a calendar date using NLCONVCUSTDATE
  you cannot do this for *1900-1927*.

  This intrinsic interprets yy/mm/dd, yy = 00-27, as CALENDAR year 100-127
  (meaning 2000-2027) and 28-99 as CALENDAR year 1928-1999.

  NL intrinsics accepting CALENDAR format accept year from 0 to 127 for
  1900-2027.

--
Gopi ([log in to unmask])
CSY R&D India, Bangalore.

ATOM RSS1 RSS2