hi,

clipka <ano### [at] anonymousorg> wrote:
> >> ... sure it's not simply an artifact of the way you observe this number?
> >
> > there's more than one way to read it? :-)
>
> As far as I'm aware, POV-Ray for Windows only reports the token count in
> the status line, so the count disappears as soon as the render proper
> starts.

same for the *nix version, afaict.

when needed, I capture terminal io with:

  $ script mylog.txt
  $ povray ...
  $ exit

and have complete "transcript" for later.

> I take it you're not running Windows then. (Sorry, I tend to not keep
> track of who runs which OS.)

not anymore.  my household is 100% Microsoft-free.  (well, I kept the fonts :-))

> > curiously, the alpha reports the "no objects in scene" warning one line earlier
> > than the x.tokenizer versions.
>
> Not much of a surprise there. Line number counting has been rewritten
> from scratch, and may differ in how it behaves at the end of the file.

ok.

> >> That said, the main focus of this version is on furthering my
> >> understanding of what's left of the legacy parser code. ...
> > ah, I might not be much help here, I have no code requiring earlier than 3.6,
> > still, I'll keep using the latest x.tokenizer as the day-to-day version.
>
> Sorry, misunderstanding I guess. The term "legacy" above wasn't
> referring to language constructs (as in e.g. v3.7 vs v3.0 scene
> language), but rather the parser itself (as in alpha vs. x.tokenizer
> parser code).

ah yes, I (now) see you wrote legacy parser.  so, so far then, six scenes
tested, all run slower in the alpha (all versions self-compiled etc).


regards, jr.

Post a reply to this message