Currently it is undefined. I may have had vague thoughts of using a negative value to mean unspecified or something like that in a scenario where the user doesn't really care and just wants the implementation to pick an optimal value.
--Rafael On Tue, Sep 4, 2012 at 5:13 PM, Darryl L. Pierce <dpie...@redhat.com> wrote: > What is the expected behavior should an application attempt to receive > messages with a negative n value? Should that API be an unsigned value > instead? > > -- > Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. > Delivering value year after year. > Red Hat ranks #1 in value among software vendors. > http://www.redhat.com/promo/vendor/ > >
