Kevin Powick wrote:
Quote:
code stopped the error. *I don't know how @Functions are resolved
internally to D3...
Dude, didn't you read my last blog?
nospamNebula-RnD.com/blog/tech/mv/d3/2010/02/d3shell2.html
1) Does not explain how @functions, such as @USER, are actually
resolved internally to D3. ie., There is no dm,bp, that one can go
look at. |
Every datum needs to be resolved differently, no? I thought that
fields like @User and @Account get pulled from the user workspace. It
seems more likely now that they might be getting @User from PIBS
dynamically on each request. I'm fairly certain @PIB does get pulled
from workspace (or R0 or R1, don't recall) while @Date and @Time
certainly do not. And I'd hope that @AM and other markers are
returned as constants (though I think these values are still stored at
the high end of the PCB). Dunno. Doesn't matter. Internals are
subject to change.
Maybe I made a mistake in lumping @vars and environment variables
together into a single category. Vars like @User, @Date, and @AM are
all resolved differently, but they're presented under a common façade.
These aren't environment variables at all really, in the way I defined
them in the article. The @var notation is more of a common mechanism
for getting access to static and dynamic data, but there is no common
means by which @vars are resolved. MV developers can plug into that
to create their own @vars, and as with the documented D3 @vars, people
are free to implement how their vars work in any way they wish - and
it's subject to change.
BTW, Kevin - you asked me recently about doing functions in D3. @vars
are the closest thing available at the moment.
Quote:
2) Four pages.. zzzzzzzzzzzzzzzzzz ;-) |
It's less than 2000 words, which is standard article size. I just
broke it into 4 pages to keep pages smaller.
T