Date: Sun, 15 Nov 2015 10:26:15 -0800 From: NGie Cooper <yaneurabeya@gmail.com> To: Allan Jude <allanjude@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues? Message-ID: <2C639B6D-578D-4D23-8863-44F9DD74C693@gmail.com> In-Reply-To: <5648CBA1.9010300@freebsd.org> References: <0650CA79-5711-44BF-AC3F-0C5C5B6E5BD9@rdsor.ro> <5648C964.2020405@freebsd.org> <2DF061E9-2541-4B10-9744-C49C515FF672@gmail.com> <5648CBA1.9010300@freebsd.org>
index | next in thread | previous in thread | raw e-mail
> On Nov 15, 2015, at 10:14, Allan Jude <allanjude@freebsd.org> wrote: … > You can setup an atexit() call to call xo_finish automatically when the > program exits. The original changes to uptime had a few other issues, > which I fixed. Programmers are lazy. Telling someone “you need to setup an atexit handler that calls xo_finish” will be met with teeth gnashing and complaints (I’ve had to deal with a bunch of people who complain that FreeBSD is not Linux at $work; I don’t have any interest in fighting developers over stuff like this). > Yes, but, a typo in any change is likely to cause a problem. This is not > a problem unique to libxo. Yes, but there’s a big difference between a typo in !libxo with the meta language, and a typo in libxo. Typo in !libxo: typos visible, unless it was something silly like mis-spelling \n (which doesn’t seem to happen much); typo in libxo: xo_emit call is invalid (no output)/segfaults. Fortunately libxo seems to support __printflike :). Thanks, -NGiehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2C639B6D-578D-4D23-8863-44F9DD74C693>