The OpenMP Forums are now closed to new posts. Please visit Stack Overflow if you are in need of help: https://stackoverflow.com/questions/tagged/openmp
A better method would be to make priority relative to the priority of the current task, with positive or negative values. Perhaps even allowing negative priority values. Then you'd need a minimum value, but the minimum need not be the default. Failing any of that, at least an API routine to return the priority of the current task.
Counterarguments that "It's just a hint!" or "The implementation can ignore priorities!" or "You can't rely on priorities anyway!" are all stupid. If priorities aren't important, remove them and simplify the spec and all implementations. if they aren't important, they shouldn't be added. If they are important, they need to promote interoperability.