Ray Gardener wrote:
> Hmm... looking back at the original post, I think the problem is that, 
> while the error is caught, it's not properly handled, for two reasons:
> 
> 1) The error messages don't say what the real problem is; the user
>    might be able to deduce that a filename with non-ASCII chars is
>    the problem, or he may not.

This is not include file specific, it is done that way for all strings. 
I.e. if you declare a string and pass that to the include directive, you 
have no way to handle it much better anyway. That one has to lok up for the 
first message to deduce the actual cause of a problem is not POV-Ray 
specific, it is common to all parsed languages...

	Thorsten

Post a reply to this message