[interfacekit] Re: BMessageRunner: negative interval

Tyler Dauwalder wrote:
>>Err, I guess, I sent my mail a bit early. I was wrong with my
>>suspicion, that the messages are sent with maximal speed. If the
>>supplied time interval is smaller than a minimal value (50000 if it
>>isn't machine dependent), then this minimal interval is used instead.
>>This is also the case for negative values. So if I copy this behavior,
>>I think, for consistency the handling should be the same for 0,
>>shouldn't it?
> 
> And now that you mention it, I have similar question wrt 
> BRoster::GetRecentDocuments and friends. Anytime there is at least one 
> recent item to return (i.e. any supplied filtering mime type or app sig 
> didn't rule out every possible item in the list) and the given number 
> of "maximum items to return" is <= 0, the function returns one item. 
> The idea of returning zero items is not undefined, however, as that is 
> what the function does when the supplied mime type filter doesn't match 
> any of the items in the list. Thus, it makes more sense to me to return 
> zero items if the maxCount parameter is <= 0 (the functions themselves 
> return void, so there's no error code to return). Any objections?

The big question is whether the changes will break reasonable existing 
code.  If it won't, in your judgement, then go ahead.  Otherwise, cleave 
to the conservative course of implementing the existing behaviour.  The 
safest thing to do, in my opinion, would be to also have the 
implementation for existing behaviour there (commented or #if 0'd out) 
so that we can easily switch to it if testing/real world use shows the 
changes to be problematic.

e

Other related posts: