Date: Mon, 1 Jan 2018 08:57:18 -0800 From: Larry McVoy <lm@mcvoy.com> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> Cc: Larry McVoy <lm@mcvoy.com>, Poul-Henning Kamp <phk@phk.freebsd.dk>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Is it considered to be ok to not check the return code of close(2) in base? Message-ID: <20180101165718.GI4678@mcvoy.com> In-Reply-To: <201801011652.w01GqvCx087076@pdx.rh.CN85.dnsmgr.net> References: <20180101161817.GF4678@mcvoy.com> <201801011652.w01GqvCx087076@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 01, 2018 at 08:52:57AM -0800, Rodney W. Grimes wrote:
> > On Mon, Jan 01, 2018 at 04:14:33PM +0000, Poul-Henning Kamp wrote:
> > > But this is bikeshedding at this point anyway.
> >
> > +1
>
> Bike shedding is good, people learn things from it. I never knew that
> assert was altered by NDEBUG for example, thanks for that enlightenment
Um, does the FreeBSD man page not start like the Linux man page with
If the macro NDEBUG was defined at the moment <assert.h> was last
included, the macro assert() generates no code, and hence does nothing
at all.
?
And bikeshedding has the effect of making people hit the delete key. I've
deleted without reading about 80% of this thread. So if there was signal
in that 80%, I for one, did not get it.
And the amount of back and forth on something that is this basic is sort
of mind numbing. As a new person on FreeBSD it doesn't show the project
in a good light. Just sayin.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180101165718.GI4678>