This appears to be my night for finding bugs in POV-Ray.  First, I found an
apparent bug in the CodeMax editor (see povray.windows), then I found the
triangle mesh bug in the Superpatch, and now this:

In UVPov 5.4, it appears that the parser expects a white space of some sort
at the end of every file.  If it does not find this, it gives the error
message "Unexpected end of file found."

Mark

Post a reply to this message

Mark Wagner wrote:
> 
> This appears to be my night for finding bugs in POV-Ray.  First, I found an
> apparent bug in the CodeMax editor (see povray.windows), then I found the
> triangle mesh bug in the Superpatch, and now this:
> 
> In UVPov 5.4, it appears that the parser expects a white space of some sort
> at the end of every file.  If it does not find this, it gives the error
> message "Unexpected end of file found."
> 
> Mark

This was an official version bug that has been corrected by the Pov team. I
imagine once Chris releases the windows source code for v3.1g this fix will
make it into our popular pov patches as well.

-- 
Ken Tyler
  
mailto://tylereng@pacbell.net
http://home.pacbell.net/tylereng/links.htm

Post a reply to this message

Ken wrote:
> 
> Mark Wagner wrote:
> >
> > This appears to be my night for finding bugs in POV-Ray.  First, I found an
> > apparent bug in the CodeMax editor (see povray.windows), then I found the
> > triangle mesh bug in the Superpatch, and now this:
> >
> > In UVPov 5.4, it appears that the parser expects a white space of some sort
> > at the end of every file.  If it does not find this, it gives the error
> > message "Unexpected end of file found."
> >
> > Mark
> 
> This was an official version bug that has been corrected by the Pov team. I
> imagine once Chris releases the windows source code for v3.1g this fix will
> make it into our popular pov patches as well.

Here are the changes between public POV-Ray 3.1 and 3.1c

3.1c               1/29/99 Chris Young
Fixed radiosity preview with odd screen size.
Reinitialized max_trace_level & radiosity_trace_level properly
--->>>> Fixed token at end of file with no cr/lf or newline

-- 
Ken Tyler
  
mailto://tylereng@pacbell.net
http://home.pacbell.net/tylereng/links.htm

Post a reply to this message

The reason for this is that UVPov was started from the POV-Ray 3.1a code
base, and it was not fixed until 3.1c (as Ken pointed out).  I've kept on
top of most of the bug fixes, but I have missed some of them.  If anyone
knows what I have to change to fix this, let me know and I will.

-Nathan

Mark Wagner wrote:
> 
> This appears to be my night for finding bugs in POV-Ray.  First, I found an
> apparent bug in the CodeMax editor (see povray.windows), then I found the
> triangle mesh bug in the Superpatch, and now this:
> 
> In UVPov 5.4, it appears that the parser expects a white space of some sort
> at the end of every file.  If it does not find this, it gives the error
> message "Unexpected end of file found."
> 
> Mark

Post a reply to this message

Nathan Kopp <Nat### [at] koppcom> wrote:
: The reason for this is that UVPov was started from the POV-Ray 3.1a code
: base, and it was not fixed until 3.1c (as Ken pointed out).  I've kept on
: top of most of the bug fixes, but I have missed some of them.  If anyone
: knows what I have to change to fix this, let me know and I will.

  Why don't you just use the latest povray source instead of duplicating
the bug fixes to your old 3.1a version? I can imagine it's a lot of
wasted time.

-- 
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

DOS, MacIntosh, Linux and Unix are 3.1g but Windows platform
(UVpov-based pvengine) is still 3.1a at www.povray.org last I saw.


Nieminen Mika wrote:
> 
>   Why don't you just use the latest povray source instead of duplicating
> the bug fixes to your old 3.1a version? I can imagine it's a lot of
> wasted time.

Post a reply to this message

On Sat, 17 Jul 1999 18:04:08 -0400, Nathan Kopp wrote:
>The reason for this is that UVPov was started from the POV-Ray 3.1a code
>base, and it was not fixed until 3.1c (as Ken pointed out).  I've kept on
>top of most of the bug fixes, but I have missed some of them.  If anyone
>knows what I have to change to fix this, let me know and I will.

The fix is in the Echo_getc() function in tokenize.c.  You can find the
fixed code in the official 3.1e/3.1g source or in the superpatch.

Post a reply to this message

Nieminen Mika wrote:
> 
>   Why don't you just use the latest povray source instead of duplicating
> the bug fixes to your old 3.1a version? I can imagine it's a lot of
> wasted time.
> 

Actually, it _saves_ time.  The photon mapping patch consists of many
small changes to a variety of files in POV-Ray (mostly scattered around
in lighting.c). Taking a fresh source and making all those changes is
quite a time-consuming task (I've spent hours incorporating it into
the superpatch).  Plus, I want to know exactly how various bugs have been
fixed, so I like to apply the fixes myself.  And on top of that, I have
made a plethora of other changes to POV that I would also have to
incorporate into the new source every time I want to update to a new
code base.

-Nathan

P.S.  I am not experienced with the diff tools, so I do updates by hand.
Maybe someday I'll get around to learning how to use diff.

Post a reply to this message

Nathan Kopp <Nat### [at] koppcom> wrote:
: The photon mapping patch consists of many
: small changes to a variety of files in POV-Ray (mostly scattered around
: in lighting.c). Taking a fresh source and making all those changes is
: quite a time-consuming task

  This is one reason why modularity is a very good thing in programming...
  Perhaps povray4 will be more modular and more easy to change.

-- 
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

On Mon, 19 Jul 1999 23:41:05 -0400, Nathan Kopp wrote:
>P.S.  I am not experienced with the diff tools, so I do updates by hand.
>Maybe someday I'll get around to learning how to use diff.

You really should.  The superpatch would never have happened without 
the help of diff, diff3, and some cobbled-together perl scripts.  I
was even able to treat the 3.0 -> 3.1 transition in the official code
as just another (huge) patch.

Post a reply to this message