Hi Przemek,
Ok, so let's say we have PRI_IDLE, but as soon as we can go down a
step we
need a way to go up a step to return to the regular class of
priority and so
we have PRI_REGULAR.
This is not a problem of changing priority (though even this is OS
dependent and some things will not be fully portable) but replicating
compatible behavior between OS-es. The IDLE priority is esy to define
as do sth when other threads do nothing and can be quite easy reach
in all OSes and such priority does not change other threads behavior.
Other states different then regular one will change efectively change
the priority of other threads.
I'd happily settle with a DEFAULT and an IDLE state then.
I think that such a three levels system would be ok for every real
need (apart
from some fancy cases, which can be solved by each programmer
writing some C
code).
I'll add the interface for priority changing but it should be
documented
that code which uses it may behaves differently in different OSes.
Well, please make it C level only, or .prg level but in the
__*() namespace in this case. Let's try to keep the .prg level
coherent as much as we can. Probably very few users will need
these extra levels anyway, and those are probably able to
tackle a few .c code to reach the special features.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
