It sounds as though they are already planning to incorporate an HPCENTURY
variable. It is simple enough to create a new variable using
concatenation. Also, HPs hallmark is its backward compatibility. If, in
addition to HPCENTURY, another variable consisting of CCYY is needed, I
would recommend HPYEARF. The 'F' stands for formatted. It should
probably be comprised of CCYYMMDD. This would retain the flavor of:
HPDATE = 21
HPDATEF = THU, NOV 21, 1996
Carl Hughes
Don Harrington writes:
My personal preference (aren't they all?) is for a four-digit year
instead of a century variable. If a century variable is _really_ needed,
one could be extracted from the four-digit year.
On Wed, 20 Nov 1996, M Gopalakrishnan wrote:
> Hi
>
> We are currently in the process of adding new CENTURY variable for
> MPE/iX.
>
> Proposed HPCENTURY CI variable would return the century component
> (first two digit of the current year) corresponding to the HPYEAR
> CI variable. For example,
>
> In 1997, HPYEAR = 97 and HPCENTURY = 19
> 2000, HPYEAR = 00 and HPCENTURY = 20
> 2001, HPYEAR = 01 and HPCENTURY = 20 and so on.
>
> Hence, we would be having HPCENTURY and HPYEAR variables to get the
Year.
>
> Question : Do you need (how important it is) to have a new CI variable
for
> four-digit year, having 1997 for Year 1997, 2000 for Year
2000,
> and so on?. If you need, what would be the better name for
the
> variable? (one suggestion is : HPYEAR4).
>
> I am working with Kishore ([log in to unmask]) on the new date
intrinsics
> proposal. The proposal will be available to this newgroup/3000-L for
> discussion in the week starting 26 Nov 96.
>
> Thanks and regards,
>
> Gopi ([log in to unmask])
> CSY R&D India, Bangalore.
>
Don Harrington Boeing Commercial Airplane Group
(206) 931-4457 voice P. O. Box 3707 M/S 5J-34
(206) 931-9085 FAX Seattle, WA 98124-2207
[log in to unmask]
These thoughts are owned by the person expressing them, and no one else!
|
