[EMAIL PROTECTED] wrote:
> Hi Petr,
>
> Well, it can, just that right now it isn't. ;-) Put in a request for it if
> you think it's important.
;-) Why should I? Isn't it a little bit inconsistent and so shouldn't it be put
into request queue automatically? You know, I'm just lazy :-)
-pekr-
>
>
> - jim
>
> Maybe At 09:09 AM 10/29/99 +0200, you wrote:
> >Hi Jim,
> >
> >
> >->> t: now
> >->> t/julian
> >== 302
> >
> >->> now/julian
> >** Script Error: now has no refinement called julian.
> >** Where: now/julian
> >
> >What's the difference in assigning t: now, printing t/julian, and direct
> >call of
> >now/julian? So why can't /julian become refinement of 'now?
> >
> >-pekr-
> >
> >[EMAIL PROTECTED] wrote:
> >
> > > Hi,
> > >
> > > Try this:
> > >
> > > >> t: now/date
> > > == 28-Oct-1999
> > > >> t/julian
> > > == 301
> > > >> 1-jan-1999 + 300
> > > == 28-Oct-1999
> > >
> > > - jim
> > >
> > > At 09:56 PM 10/28/99 -0700, you wrote:
> > > >REBOL *must* be basing dates on a stored Julian day number. They should
> > > >give us a word 'julian that returns the julian day no for a given
> > date, and
> > > >some other word to convert it to a date. The Julian day number
> > accounts for
> > > >leapyears, number of days in each month, etc. There are a number of
> > "epoch"
> > > >dates corresponding to Julian day number zero. EG 1 jan 1978, another
> > in the
> > > >15 or 14 century, etc.
> > > >
> > > >----- Original Message -----
> > > >From: <[EMAIL PROTECTED]>
> > > >To: <[EMAIL PROTECTED]>
> > > >Sent: Thursday, October 28, 1999 8:53 PM
> > > >Subject: [REBOL] epoch? Re:(4)
> > > >
> > > >
> > > > > You mean to use 31-12-1969
> > > > >
> > > > > At 10:40 PM 10/28/99 -0400, you wrote:
> > > > > >Elegant, except it's one day off ... should be now - 12-31-1969 *
> > 86400,
> > > > > >except that gives an invalid date.
> > > > >
> > > > >
