Re: new errno ?

The DOMAIN and RANGE errno values are not really used outside floating-point code, and are...conceptually appropriate...to many other kinds of problems. Thor On Fri, Jul 06, 2018 at 03:59:12PM -0700, Jason Thorpe wrote: > > > > On Jul 6, 2018, at 2:49 PM, Eitan Adler wrote: > > > > For those

Re: new errno ?

Date:Fri, 6 Jul 2018 13:46:42 -0600 From:Warner Losh Message-ID: | Poul-Henning added it to differentiate between potentially valid but not in | this combo (EINVAL or EFAULT) and args that are clearly programming errors | (EDOOFUS), but in code that couldn't

Re: new errno ?

On Fri, Jul 6, 2018, 2:10 PM Greg Troxel wrote: > > Phil Nelson writes: > > > Hello, > > > > In working on the 802.11 refresh, I ran into a new errno code from > FreeBSD: > > > > #define EDOOFUS 88 /* Programming error */ > > > > Shall we add this one? (Most likely

Re: new errno ?

> On Jul 6, 2018, at 2:49 PM, Eitan Adler wrote: > > For those interested in some of the history: > https://lists.freebsd.org/pipermail/freebsd-hackers/2003-May/000791.html > ...and the subsequent thread went just as