I notice this a lot in the SDK. The onus on handling for every evetuality is typically on the plug. This causes plugins to require large chunks of preprocess logic and make non-trivial standard optimisations. Simple things like making it law not convention that event lists are sorted, or setting the rule that block sizes are always even. The irony is that the host would only need to verify that these criteria were met once per process block, whereas passing the buck to the plugin ensures that they are checked for and defended against as many times as there are plugins active.madgav wrote:I argued the toss with Charlie S over this a couple of years ago trying to promote the position that plugins should be as simple as possible.
ProcessEvents()
-
- KVRAF
- Topic Starter
- 4644 posts since 28 Nov, 2002 from Chicago
Thanks for the feedback people, I'll have a little rethink about how processing incoming events.
Someone shot the food. Remember: don't shoot food!