In article <394D8D71.42B5626F@nospam.hotmail.com> , Pabs 
<pab### [at] nospamhotmailcom>  wrote:

> These UICB_xxs are all very well but
> 2 probs
> 1.
> Of the src I have looked at (win, dos, unix, linux) none of the config.h
> files
> define these and so they all resolve to nothing in frame.h like so
> #ifndef UICB_PARSE_ERROR  /* Alert UI that a parse error occurred */
> #define UICB_PARSE_ERROR
> #endif

This is exactly how all POV-Ray config.h macros work!  If you don't use them
POV-Ray defines a useful default.  Without this you would have to fix every
config.h of every platform whenever you add a new platform configuration
macro.

> Does the mac config.h define these (I can't read hqx files) & if so why don't
> other platforms use them

Why? Simple: POV-Ray is a complex software and these macros were added late
in the 3.1 development and other platform source code was just not adapted
in time before the 3.1 release.  This happens :-)

> 2.
> Even if they were defined there is no define corresponding to the
> WIN_WhereError function - just the following 4 defines
> UICB_PARSE_ERROR  /* Alert UI that a parse error occurred */
> UICB_USER_ABORT  /* alert UI that user aborted the render */
> UICB_OPEN_INCLUDE_FILE  /* alert UI that an include file was opened during
> parse */
> UICB_CLOSE_INCLUDE_FILE  /* alert UI that an include file was closed during
> parse */
> so maybe a define of UICB_WhereError could be added in config.h & frame.h to
> alert the UI of where in the file the parsing error occured
> & in Where_Error this funcion could be called
> Only WinPOV calls this kind of function

UICB_PARSE_ERROR provides the same functionality WIN_WhereError does, it has
just a different name (Where_Error only gets called on parse errors).  It
does not need to be in Where_Error. The place it is in is fine to provide
the same functionality (in function Error in userio.c), but if you don't
like UICB_PARSE_ERROR in userio.c just move (not copy!) it to tokenize.c.

> I can't find these UICB macros in the unix src (frame.h et al.)

I do not know why this is the case. Are you sure you are loking at the 3.1g
Unix source code? It should be in any 3.1.

> Anyway just for the hell of it could Nathan PLEASE add the call I mentioned
> in my previous post to the next version of WinMegaPOV - even if it is just
> for the compiled binary.

Adding it would serve no purpose as it is already there, I fail to
understand the logic behind it then - sorry :-(


    Thorsten


____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message