"Thorsten Froehlich" wrote:
> No, it takes the string. It just doesn't
> output the contents of the string.

And that's the problem. The documentation clearly says that it's supposed to
take it *and* output it. Once again I quote the same part:

"There are seven distinct text streams that POV-Ray uses for output. You may
output only to three of them."

If you still insist it isn't a bug, then what is the reason that it requires
a string, if the contents of the string isn't used for anything at all? What
is the reasoning behind this "feature"?

From another of your replies:

> Please estimate the probability that a user who
> doesn't know about the #error directive (which is
> in the documentation) will look up the reason for
> an error in the documentation...

I think it's high, but I don't have any statistics to base it on. If you
have I'd be interested in seeing them. If not, then it's pointless to
discuss this.

Instead, you you tell me why the current behavior is less confusing for the
user than the proposed behavior? If we can't find a perfect solution, then
we just ought to take the best available. From here I refer you to the reply
posted by Warp.

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