On Thu, 1 Nov 2001 15:10:28 +0100, "Rune" <run### [at] mobilixnetdk> wrote:

> > Bug with parse_string
> > http://news.povray.org/9pk0rto8s07dnm320f5m503aqu43ak6g3p@4ax.com
>
> This one is not a bug.

Why ?

You maintained this within your list as bug (so someone confirmed it) and I
don't see any discussion about it ? So what changed ? Perhaps compiler platform.
But it still not work with beta 7. Example attached to bugreport is only
example. I have designed large system based on Parse_String (many times called
Parse_String) and within generated files parser reports nonsesnse content (but
content of files is ok). And my system works fine when I replace content of
Parse_String with 

#declare Parse_String_Counter=0;
#macro Parse_String(String)
    #local File_Name=
        concat("parse_string_",str(Parse_String_Counter,0,0),".tmp")
    #fopen FOut File_Name write
    #write(FOut,String)
    #fclose FOut
    #declare Parse_String_Counter=Parse_String_Counter+1;
    #include File_Name
#end

So I think povray is not prepared to twice read/write the same file with
different content. Now I found your post that it is rather limitation. If this
is confirmed limitation by the Team then it is sad fact for me. I found way to
make simple OOP for SDL with this.

There is another thing connected with Parse_String reported by me and not
included anywhere (no answer, no list entry, no change within documentation)
http://news.povray.org/tlstqtsgocagvejfs6knd6buql6tqo2qn3@4ax.com

ABX
--
#declare _=function(a,b,x){((a^2)+(b^2))^.5-x}#default {pigment{color rgb 1}}
union{plane{y,-3}plane{-x,-3}finish{reflection 1 ambient 0}}isosurface{ //ABX
function{_(x-2,y,1)|_((x+y)*.7,z,.1)|_((x+y+2)*.7,z,.1)|_(x/2+y*.8+1.5,z,.1)}
contained_by{box{<0,-3,-.1>,<3,0,.1>}}translate z*15finish{ambient 1}}//POV35

Post a reply to this message