diff options
| author | Vito Caputo <vcaputo@pengaru.com> | 2023-05-11 12:48:42 -0700 |
|---|---|---|
| committer | Vito Caputo <vcaputo@pengaru.com> | 2023-05-11 15:19:25 -0700 |
| commit | 2b9eca8724fe6c5e0f6a4438cd398b5978283131 (patch) | |
| tree | 6e78ff7b7269926ddda6eb944cc2c97237e11b97 /src/modules/strobe | |
| parent | caa75150ab4982c5ca0e48e606dd4f81087e7a3d (diff) | |
modules/*: remove use of static default setups
There was a time when it made sense for context creates needing
setups but not receiving them to still be functional with some
sane defaults.
But with recursive settings, we really shouldn't ever have
orphaned nested module uses unreachable by a proper setup.
So let's just get rid of this fallback, and exclusively rely on
the baked setups provided by the .setup() methods. They still
have preferred defaults, and the proper setup production
machinery is what should be responsible for applying those
at runtime where they may also be overridden or otherwise
influenced.
Diffstat (limited to 'src/modules/strobe')
| -rw-r--r-- | src/modules/strobe/strobe.c | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/src/modules/strobe/strobe.c b/src/modules/strobe/strobe.c index fa245f7..4d56045 100644 --- a/src/modules/strobe/strobe.c +++ b/src/modules/strobe/strobe.c @@ -35,18 +35,10 @@ typedef struct strobe_context_t { } strobe_context_t; -static strobe_setup_t strobe_default_setup = { - .period = STROBE_DEFAULT_PERIOD, -}; - - static til_module_context_t * strobe_create_context(const til_module_t *module, til_stream_t *stream, unsigned seed, unsigned ticks, unsigned n_cpus, char *path, til_setup_t *setup) { strobe_context_t *ctxt; - if (!setup) - setup = &strobe_default_setup.til_setup; - ctxt = til_module_context_new(module, sizeof(strobe_context_t), stream, seed, ticks, n_cpus, path); if (!ctxt) return NULL; |