[asterisk-users] Problems with new logic being 'n' option to Queue in 1.4.9

[James FitzGibbon]

On 7/27/07, Mark Michelson <mmichelson at digium.com> wrote:

> Could you submit this as an issue on the bugtracker? The 'n' option was
> mucked with just prior to the 1.4.9 release and so any problems
> experienced with it should be reported there so they can be fixed as
> quickly as possible.



It's been submitted; to clarify though the change made in 1.4.8 related to
the 'n' option doesn't seem to cause this.  1.4.8 (with or without the 'n'
option) does what I'd expect it to.  It's the logical overloading of go_on
in 1.4.9 that broke things.  go_on used to be a boolean - now it's a
dual-valued variable.  Sometimes it's compared just for it's truthfulness,
and sometimes it's used in a numeric comparison against the queues's
membercount.

If go_on had been left alone and a new variable used to store the threshold
to be compared against membercount, I don't think 1.4.9 would have broken
things, because go_on would (in my configuration) never have been set to
anything but zero, preventing the numeric comparison against membercount
from ever being performed.

-- 
j.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070727/8a05614e/attachment.htm