POV-Ray : Newsgroups : povray.pov4.discussion.general : Caching parsed code : Re: Caching parsed code Server Time
2 May 2024 20:49:45 EDT (-0400)
  Re: Caching parsed code  
From: nemesis
Date: 16 Apr 2009 00:35:24
Message: <49e6b58c@news.povray.org>
clipka wrote:
> nemesis <nam### [at] nospam-gmailcom> wrote:
>> Friggin' insane.  Without even peeking at the code, I'm guessing the
>> lack of proper scoping rules has something to do with that as #locals
>> are locals in the context of files, not of macros... or am I wrong again?...
> 
> Um... I think you are. #locals are indeed locals in the context of include files
> as long as they're not inside macros - but when they're inside macros, they're
> local to that one.

I assumed files were reopened when calling macros exactly to provide 
them with some clucky local context. :P  If not, I don't see the reason 
for the reopening...

I'll dig in now, but since my point is replacing all that, I don't think 
I'll lose my time trying to understand it in the first place... :P

> Yeah. Think of it: If we had pre-compiled bytecode include files, how could we
> ever copy & paste the macros into our main scene files for speedup? :P

Oh, almost forgot pre-compiled includes... but not to scare people off 
it's worth reminding it should be something akin to how Python does, 
source and bytecode side-by-side.  It just loads the bytecode if already 
compiled and if not, compiles and stores for next time.


Post a reply to this message

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