3 ms·
The way you describe it as "time" and "history" is confusing. In your gist, essentially you want to roll backwards, fetch the value you had in the previous laye
by Smudge 14y ago
The way you describe it as "time" and "history" is confusing. In your gist, essentially you want to roll backwards, fetch the value you had in the previous layer of the stack, and then jump forward to your current execution, but with that reference in tow. So I think I get where you're going, but it doesn't seem very useful to me. The whole point of passing the reference when you need it is that you're giving your code some meaningful context. If any reference were accessible from any method, you'd essentially be dealing with a giant global context of everything. (Isn't that what singletons are for?)
- Meai 14y agoYou are thinking way too much in terms of programming. What's wrong with global context? Your mind is one huge global context, and it seems to work fine. You fetch stuff all the time from one big pool. Sure, there's hierarchy in there. Just like in my example: Different times, different functions, they all provide hierarchy and structure to the times you can fetch data from.
- catharsis 14y agoThis sounds like state based programming. IIRC this was a moderately popular way of programming games in the past. The resulting code is somewhat monolithic however, hard to maintain.