![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Dammit, and I had some important work to do...
Oh well, it will have to wait. Gotta see them photons in media!
Margus
Nathan Kopp wrote:
>
> Well, I've uploaded UVPov 6.1. Lots of bug fixes. Plus photons in media.
> :-)
>
> Have fun. And continue with the polite and informative bug reports
> (including demo scenes). They do help a lot.
>
> -Nathan
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
No fractal patch included?
--
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
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
I think that would require a bigger version change, like 7.0.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
I wanted to clobber those bugs, first (before potentially introducing more).
And I had already started on media photons. Adding the fractal patch will
probably be in versio 6.2 (version 7.0 should hopefully include a bunch of
superpatch features... provided days start lasting 26 hours).
-Nathan
TonyB <ben### [at] panama phoenix net> wrote...
> I think that would require a bigger version change, like 7.0.
>
>
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Hello Nathan!
You are very fast to correct bug!!! Personally, I appreciate very much
:)!!!
Fabian.
Nathan Kopp wrote:
>
> Well, I've uploaded UVPov 6.1. Lots of bug fixes. Plus photons in media.
> :-)
>
> Have fun. And continue with the polite and informative bug reports
> (including demo scenes). They do help a lot.
>
> -Nathan
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Btw, I still can't find any reference to the ini_option command in the
documentation.
--
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
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Writing documentation is so much less fun than writing code. Anyway, I'll
document it soon (it's on my to-do list).
-Nathan
Nieminen Juha <war### [at] punarastas cs tut fi> wrote...
> Btw, I still can't find any reference to the ini_option command in the
> documentation.
>
> --
> 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
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Nathan Kopp <Nat### [at] kopp com> wrote:
: Writing documentation is so much less fun than writing code. Anyway, I'll
: document it soon (it's on my to-do list).
Thanx :)
Btw, I compiled the newest version of uvpov in this Solaris Sparcstation.
Your //-comments caused lots of trouble. There's no easy way to automatically
replace them with /* ... */. One problem is that some of the //-comments
are inside a bigger /**/-comment block, so replacing the //-comments breaks
the bigger block.
One possibility is just to automatically remove the //-comments, but that
might cause some problems too...
You have some very tricky comment lines like the line 1028 in cones.c:
//*/
It's not trivial for a line-by-line filter to see whether that is the
beginning of an //-comment or the end of an /*...*/ comment.
Also the http:// lines cause headache to the filtering.
Would it be too much asked if you could fix this?
The result was that I got most of the comments working by filtering, but
had to make some modifications by hand before it was completely fixed.
The lack of ending newline at the end of radiosit.c also caused problems
with the filtering (I still don't know why).
--
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
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
I use MSVC++, and it doesn't complain, so I always forget that they are
their (old habits die very hard). Anyway, I'll get rid of them for the next
release. Sorry about that.
-Nathan
Nieminen Juha <war### [at] punarastas cs tut fi> wrote...
> Nathan Kopp <Nat### [at] kopp com> wrote:
> : Writing documentation is so much less fun than writing code. Anyway,
I'll
> : document it soon (it's on my to-do list).
>
> Thanx :)
>
> Btw, I compiled the newest version of uvpov in this Solaris
Sparcstation.
> Your //-comments caused lots of trouble. There's no easy way to
automatically
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <3826f560@news.povray.org> , Nieminen Juha
<war### [at] punarastas cs tut fi> wrote:
> Btw, I compiled the newest version of uvpov in this Solaris Sparcstation.
> Your //-comments caused lots of trouble. There's no easy way to automatically
> replace them with /* ... */. One problem is that some of the //-comments
> are inside a bigger /**/-comment block, so replacing the //-comments breaks
> the bigger block.
Maybe you should telll your compiler to treat .c files like .cpp files. At
least the official 3.1g source code compiles well using a C++ compiler, and
I suspect the same should work for Nathan's code.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trf de
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |