> yesterday I promised bug and now I fund shortest
> version for report

First of all, as you say, this bug is not caused by the parse_string macro.
Thus the subject line of the message "bug with parse_string" is *very*
misleading. Please use descriptive subject lines.

Now let's look at the problem.

Here's some code that produces the problem without using parse_string at
all:

// start of scene
#fopen File "file.tmp" write
#write(File,"#macro Box (C1,C2) box{C1,C2} #end\n")
#fclose File
#include "file.tmp"

#fopen File "file.tmp" write
#write(File,"")
#fclose File
#include "file.tmp"

Box(<1,1,1>,<2,2,2>)
// end of scene

We basically write a macro to a file and then overwrites that file with
something else.

Macros work by parsing the code inside the macro. When that code isn't there
anymore, then the macro can't be called correctly.

I would say that this is not a bug but a limitation, so I can't confirm the
bug.

Rune
--
3D images and anims, include files, tutorials and more:
Rune's World:    http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users:   http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk

Post a reply to this message