Is POV-Ray Y2K compliant?  For example, if, using POV-Ray for Windows, I
start a rendering on New Year's Eve, will it be successfully rendered if
rendering continues past midnight?

Mark

Post a reply to this message

Hmm, why not set your clock to 11:55 PM Dec 31, 1999 and start rendering.
In 5 minutes you'll know.

My guess is POV-Ray doesn't give a rats ass about the date, but I could be
wrong.

-Mike

Mark Wagner wrote:

> Is POV-Ray Y2K compliant?  For example, if, using POV-Ray for Windows, I
> start a rendering on New Year's Eve, will it be successfully rendered if
> rendering continues past midnight?
>

Post a reply to this message

Mark Wagner <mar### [at] gtenet> wrote:
: Is POV-Ray Y2K compliant?  For example, if, using POV-Ray for Windows, I
: start a rendering on New Year's Eve, will it be successfully rendered if
: rendering continues past midnight?

  I'll answer with another question:
  Can you tell me any reason why it shouldn't?

  AFAIK, there's no "if (date(now) < date(before)) StopRendering();" line in
povray.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Actually, what will happen is that it will cause a huge failure at your
local sewage plant.  You will wind up with 2,000,000 gallons of raw sewage
in your yard (only if you live in Los Angeles ...)  :<)

--
Jim

Check out my web site  http://www.kressworks.com/
It'll blow your mind (politically), stimulate your senses (artistically)
and provide scientific insights that boggle the mind!

Mark Wagner <mar### [at] gtenet> wrote in message
news:376b3b2e@news.povray.org...
> Is POV-Ray Y2K compliant?  For example, if, using POV-Ray for Windows, I
> start a rendering on New Year's Eve, will it be successfully rendered if
> rendering continues past midnight?
>
> Mark
>
>

Post a reply to this message

Jim Kress wrote:
> 
> Actually, what will happen is that it will cause a huge failure at your
> local sewage plant.  You will wind up with 2,000,000 gallons of raw sewage
> in your yard (only if you live in Los Angeles ...)  :<)
> 
> --
> Jim

You forgot to mention this will only occur if the moon is 1/4 full otherwise
it happens in New York City.

-- 
Ken Tyler

mailto://tylereng@pacbell.net

Post a reply to this message

Mark wrote:
> Is POV-Ray Y2K compliant?  For example, if, using POV-Ray for Windows, > Istart a
rendering on New Year's Eve, will it be successfully rendered
> if rendering continues past midnight?

Sort of a silly question, actually. What you really should be asking is
whether the OS will freak out (an instant crash simply won't happen no
matter what), or the power will go out (unlikely at this point).
But for a program to be "Y2K-compliant", there first has to be some
reason why it wouldn't be. Anything that works with a date could perhaps
be suspect; but POV is simply a number cruncher, so it doesn't fall into
that category. And typically, date-related programs couldn't crash
either--they'd just cause some screwy result to happen.
This is sort of like asking if a program that adds 2+2 will crash if
your printer suddenly stops working--unless it's using the printer, the
program doesn't care.

Lummox JR

Post a reply to this message

Lummox JR wrote in message <376### [at] aolcom>...
>Mark wrote:
>> Is POV-Ray Y2K compliant?
>
>Sort of a silly question, actually. What you really should be asking is
>whether the OS will freak out (an instant crash simply won't happen no
>matter what), or the power will go out (unlikely at this point).
>But for a program to be "Y2K-compliant", there first has to be some
>reason why it wouldn't be. Anything that works with a date could perhaps
>be suspect; but POV is simply a number cruncher, so it doesn't fall into
>that category. And typically, date-related programs couldn't crash
>either--they'd just cause some screwy result to happen.
>This is sort of like asking if a program that adds 2+2 will crash if
>your printer suddenly stops working--unless it's using the printer, the
>program doesn't care.


So POV-Ray might report that the rendering took -36524d 23h 17m 23s to
render.

Mark

Post a reply to this message

Mark Wagner <mar### [at] gtenet> wrote:

: So POV-Ray might report that the rendering took -36524d 23h 17m 23s to
: render.

  If povray uses the standard C library function time() it shouldn't.
  From the man page:

DESCRIPTION

  The time() function returns the time in seconds since the Epoch. The Epoch
  is referenced to 00:00:00 CUT (Coordinated Universal Time) 1 Jan 1970.


  As you can see, there's no reference to the current year here.
  Since this counter is usually a 32-bit number, the real problem comes
in 2106 when the counter overflows.
  I think I will not live that long.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

>Is POV-Ray Y2K compliant?  For example, if, using POV-Ray for Windows, I
>start a rendering on New Year's Eve, will it be successfully rendered if
>rendering continues past midnight?

I doubt that the rendering code will be affected. However, the stats may look
funny.

I'd be more worried about Windows.


 /j

Post a reply to this message

Nieminen Mika wrote:
> 

>   The time() function returns the time in seconds since the Epoch. The Epoch
>   is referenced to 00:00:00 CUT (Coordinated Universal Time) 1 Jan 1970.
> 
>   As you can see, there's no reference to the current year here.
>   Since this counter is usually a 32-bit number, the real problem comes
> in 2106 when the counter overflows.
>   I think I will not live that long.

Unless it's storing it as a signed integer, in which case it conks out
in 2038.  I've heard plenty of references to the 2038 problem, which I
may very well live to see.  Then again, I also expect to have migrated
to 64-bit architectures by that time.

-- 
Mark Gordon
mtg### [at] povrayorg

Post a reply to this message