On Thu, Feb 03, 2000 at 01:28:33PM +0100, [EMAIL PROTECTED] wrote:
> after installing Event 0.62, I just discovered this (relatively new)
> warning in the description of the priority attribute:
>
> "You should not specify prio in the constructor. Use C<nice> instead
> for an offset from the default priority."
>
> What's the reason for this strong suggestion? I expicitly USE prio in
> ALL my constructors to build the hierarchy of watchers I need. This
> would be possible with the nice attribute as well, but nice is dangerous
> because the hierarchy then depends from Event internals (default
> priorities), which might become subject to changes. I always thought of
> nice as a "specialists" attribute (for advanced users knowing internals
> very well).
That's interesting. My thinking was that C<nice> requires less
knowledge of internals than C<prio>. With C<nice>, I can think about
increasing or decreasing priority without worrying about the exact
numeric priority. Perhaps the documentation can be changes to:
Unless you are a sophisticated user, do not specify prio in the
constructor. Use C<nice> instead for an offset from the default
priority.
--
"May the best description of competition prevail."
via, but not speaking for Deutsche Bank
