HP3000-L Archives

January 1997, 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:
"Eric H. Sand" <[log in to unmask]>
Reply To:
Eric H. Sand
Date:
Fri, 10 Jan 1997 20:12:12 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (42 lines)
In response to Wirt Atmar's observation that one(1) VAR would be
adaquate
to represent the concept of TIME (CCYYMMDDHHMMSSMMM) I totally
agree and would further sugest that to pay this concept its'
appropriate respect
I suggest that the VAR be named HPCHRONOS in deference to one of the
very first intrinsics written for the HP3000.

  From Webster's New Collegiate Dictionary:

      chron- or chrono- comb form [Gk, fr. chronos]: time
<chronogram>


                                          Eric Sand
                                          Data Research Associates
                                          [log in to unmask]


>----------
>From:  Wirt Atmar[SMTP:[log in to unmask]]
>Sent:  Friday, November 22, 1996 10:53 AM
>To:    [log in to unmask]
>Subject:       Re: [HP3000-L] Proposal for new HPCENTURY CI variable
>
>Jeff Kell writes:
>
>>But on the "micro-management" issue... I'd much prefer ONE variable
>with
>>all clock information you could substring from as opposed to the
>growing
>>number of possible individual date/time/etc variables.
>
>That would be my strong vote, too. The string would contain
>CCYYMMDDHHMMSSMMM (where the last three MMM's are milliseconds).
However
>I would be prone to name it something other than HPYYMMDDHHMMSSMMM.
>Perhaps just HPTIME.
>
>Wirt Atmar
>

ATOM RSS1 RSS2