Paul Davis wrote: > > which should it be? A mix of the three ! No seriously, I think GMPI specification should not dictate HOW to access sys and conf info, but make people sensitive to the related problems. More specifically, it should specify a context for each callback : "the following functions are intended to be called in a real-time thread" or "the following func may use any system operation but should return as quickly as possible because blah" or "Here you can block the thread waiting for user input or other signals" etc. Then to define what are the real-time issues, and what kind of calls should be avoided there. Back on the cross-platform topic, I'm ok with c) if such a specification exist, otherwise one just can encourage people to write clean cross-platform code. Actually it's more a matter of programming hygiene, like code writing rules or object modelling. You see their benefits mostly on the long-time run or on big projects. I understand that people having a limited development/support budget or very specific target platforms don't want to deal with cross-platform issues and overhead, and that they want to use only the APIs they know and trust. -- Laurent ==================================+======================== Laurent de Soras | Ohm Force DSP developer & Software designer | Digital Audio Software mailto:laurent@xxxxxxxxxxxx | http://www.ohmforce.com ==================================+======================== ---------------------------------------------------------------------- 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: //www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe