[gmpi] Re: Reqs final draft

Paul Davis wrote:
I can see lots of reasons to have all exceptions disabled (it's made for realtime apps - you don't want exceptions here more than you'd do in apps that use openGL), but what's your reason to want exceptions unmasked? 


if a plugin does a divide-by-zero, its an error on the part of the
developer AFAICT. as a host author, i would want to catch such
actions, and remove the plugin from my "graph". you can, i believe,
mask certain exceptions and allow others.


I'm going to jump in here with a different opinion. The rule should be that the plugin may never change the cpu/fpu flags. Ever. The host is free to set the state however it pleases. The thread that calls a plugin may be used in the host for lots of other things. The host has the correct context to know what the fpu state should be, and the plugin doesn't. Nor does GMPI know what the correct state should be. If we make a decision on the processor flags that is an undue burden on the host, because it may be regular switching of these flags in and out of plugins, which is not a good RT practice. If the host chooses 24 bit precision, for instance, a lot of plugins may sound bad. But the host presumably made that decision for some reason that outweighed the considerations of the plugin, so it should stand.

--
Mike Berry
Adobe Systems

----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules:  Please stay on topic.  You are responsible for your own
words.  Please respect your fellow subscribers.  Please do not
redistribute anyone else's words without their permission.

Archive: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: