POV-Ray : Newsgroups : povray.bugreports : Once again, the command line error messages : Re: Once again, the command line error messages Server Time
28 Apr 2024 04:36:16 EDT (-0400)
  Re: Once again, the command line error messages  
From: clipka
Date: 3 Feb 2014 02:52:07
Message: <52ef4aa7@news.povray.org>
Am 02.02.2014 20:28, schrieb Le_Forgeron:
> Dear Cousin Ricky,
>
> Your happiness is easy to satisfy, with a bit of early advertisement:
>
> --- a/vfe/unix/unixconsole.cpp
> +++ b/vfe/unix/unixconsole.cpp
> @@ -474,9 +474,11 @@ int main (int argc, char **argv)
>                          opts.AddCommand (*argv);
>          }
>
> +       PrintStatus (session);
>          // set all options and start rendering
>          if (session->SetOptions(opts) != vfeNoError)
>          {
> +               PrintStatus (session);
>                  fprintf(stderr,"\nProblem with option setting\n");
>                  for(int loony=0;loony<argc_copy;loony++)
>                  {
>
>
>
> The first PrintStatus dumps the classical page(s) about povray (from
> version to Support libraries). (it's a bit earlier than currently, but I
> do not find a reason to delay it to the parsing of the scene).
>
> The second is used to dump the parsing error collected during the
> examination of the command line options (and maybe more), in case of error.
>
> Windows vfe (and mac too), might enjoy such changes too.

That last sentence shows that we're doing something fundamentally wrong 
here: Ideally there should be only one piece of code to fix, for all 
POV-Ray front-ends.

This is probably also the reason for the confusion around FS#42: The 
command-line error reporting had already been made elaborate enough, but 
only in the Windows version.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.