On Tue, 15 Dec 2009, Jérémy Zurcher wrote:
the more natural way for me would be :
class Hydrogen {
void bootstrap() {
AudioEngine *ae = new AudioEngine();
...
}
Which we're already doing with create_instance().
void shutdown () {
delete ae;
...
}
Which is already done with 'delete Hydrogen::get_instance()'
and reduces the temptation to have destructor code that is
not in Hydrogen::~Hydrogen().
and to be sure that nobody mess object initialization.
Who? libHydrogen is internal to Hydrogen. Who's going to
mess with these?
about the logger thread, I forgot that H2 is about realtime
audio processing, shame on me.
No shame. It gets asked from time-to-time.
following the previous, it could be an idea to get rid of
QString usage within the core library ... ok stop me.
We need /some/ manner of dynamic strings. We found a good
workaround with the logger macros. If the logging level
isn't being utilized (a single integer check)... then it
totally skips the function call to Logger::log()... which
avoids QString badness.
So, we're only having RT violations if you have the logging
level set high. Or if there are real errors to report.
That said, if you have any ideas on how to get (or make)
some RT-safe dynamic strings... please share. I'm
interested in having that for Composite as well... so that
even when there's an error we're RT-safe.
Peace,
Gabriel
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Hydrogen-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
