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>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Nov 15, 2015, at 10:14, Allan Jude <allanjude@freebsd.org> wrote: =E2=80=A6 > 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 =E2=80=9Cyou need to setup an = atexit handler that calls xo_finish=E2=80=9D will be met with teeth = gnashing and complaints (I=E2=80=99ve had to deal with a bunch of people = who complain that FreeBSD is not Linux at $work; I don=E2=80=99t 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=E2=80=99s 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=E2=80=99t = seem to happen much); typo in libxo: xo_emit call is invalid (no = output)/segfaults. Fortunately libxo seems to support __printflike :). Thanks, -NGie=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2C639B6D-578D-4D23-8863-44F9DD74C693>