From: John Morrison (jmorrison_at_ahc.net.au)
Date: 2002-01-23 14:42:22
> We didn't learn that -- rather, you suggested it. I would say it's a
> bad idea, because there is no way you can write code for both int and
> double at the same time without #ifdef'ing every other line.
And it totally shoots down the idea of PLUG-IN modules.
IE you added it to the program WITHOUT recompiling!
> > I wouldn't do that. I think it will make the program
> > unmanageably complex and buggy. Especially
> > considering that most people here are probably working
> > on single-processor machines, so they won't see bugs
> > that we are creating.
>
> Multiple processes or multi-threading is really useful if there is
> something you *have* to keep up with, whilst there is something else
> which might get behind. For instance, if we are doing sound-output,
> this *has* to keep up, or else there will be a gap. You can't have
> the sound stop just because there is a big redraw going on on the
> screen.
Also in Stage 1 the modules need to keep up with the data stream. Depending
on the interface it may be real time data that needs to be checked
regularly.
> I'm not in favour of lots of unnecessary extra threads, though. Just
> ones that are vital for timing.
Yep I agree!
Loose threads can be a right royal PAIN!!!
John
This archive was generated by hypermail 2.1.4 : 2002-07-27 12:28:37 BST