summaryrefslogtreecommitdiff
path: root/src/libs/sig/ops_round.c
diff options
context:
space:
mode:
authorVito Caputo <vcaputo@pengaru.com>2023-07-05 10:52:05 -0700
committerVito Caputo <vcaputo@pengaru.com>2023-07-05 10:58:12 -0700
commit02cb290db43a2c6761083328d408dca63ed3d3b6 (patch)
treea420eede4e2ef5a2666a3d9e26af2800db6b0bbb /src/libs/sig/ops_round.c
parent5191d68bb76129cb2a95c62ea18d2ef9ae6605f2 (diff)
modules/rkt: resolve module_name->til_module_t in setup
With the "ref" builtin module established and seeming to work well enough, it looks unlikely we'll need access to unresolvable module names in the contexts. The thinking originally was that these names might have special syntax making them more generic. E.g something like "@/module/rkt/scenes/[1]/drizzle" for a module_name would have been supported, which would get resolved either at context create or even later (as in the ref builtin) at render time. But the ref builtin is using a path setting, so module names just stay module names. Maybe in the future a special syntax will be added for brevity reasons, but it does make the code more complicated vs. module names just being names and resolving them entirely at setup time. Anyhow, this commit does away with the module_name in the context's scenes. You can still access it via til_module_context_t.module.name anyways... it's basically just a resolution-of-name-to-context time constraint that's being codified now.
Diffstat (limited to 'src/libs/sig/ops_round.c')
0 files changed, 0 insertions, 0 deletions
© All Rights Reserved