from the hunches dept: the more source i read the more i am scratching my head about the way subroutines are avoided and code is inlined. i have counted too many references that refer to subroutines as 'bottlenecking code' and i find that puzzling. here's why.. and the hunch in detail:
for someone freely instantiating local variables on the head when they could be initialized and reused to call a parameterless function call a bottleneck is making me think that fundamentally the source is accessed as if it was data.. e.g. that it is literally semaphore'd, introducing overhead in the call..
this would restrict concurrent use of functions, be silly and bad and force one to inline as much as is being done while allowing one to call delegation bottlenecking.
this would make a lot of sense if the genesis of the outliner proved to be a single-user vision. its a hunch right now, but i'm going to go mad if it turns out that no matter how many threads one uses that code block are serialized beyond my control. ..meanwhile i use 'functions'.
here are my two favorites: ;-)
on IsDynamic()
{ local (pta=html.getPageTableAddress());
return !(pta^.radioResponder.flStaticRendering)}
on IsStatic()
{ local (pta=html.getPageTableAddress());
return (pta^.radioResponder.flStaticRendering)}