From owner-freebsd-current@freebsd.org Sun Nov 15 18:26:18 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E3E6A2FE90 for ; Sun, 15 Nov 2015 18:26:18 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 70BA218CE; Sun, 15 Nov 2015 18:26:18 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by pacej9 with SMTP id ej9so43668499pac.2; Sun, 15 Nov 2015 10:26:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=oMHHhU8VqiUqGteM8Fau4RicWL8EZp4axlkIKtclJR8=; b=L7wrtgUFtZSf2zd6qMa8gt54xTweR7RfdRCl86f/KLPlSOhOK69oOouxaVKrhpoRKc 5l3wlVbvTGop5fWZXf0McX7lerZrrPpXLOb/FufGzb5eBMEY6OkQsteo2DFXSF5Kie7N RsNAg2vDlRlUt4OvLBnWUCoEP8uSoVd/1DCqUCbqid4/UiYFjJEIc3ui3U6yulTCN8kC KHyt0RJvxhGNmVHTcmo7Dx0vXe+x4a06gjZqXVfYx++TSGY0JVsjwxwgK3ItZcaHeRpv JPIVXAn23/rIA2acF8DYUE+PYjsCeJJxFR/QYw4LZD50tA2Pyqpxg6ykFnp+x9mckOkn sNhw== X-Received: by 10.68.241.41 with SMTP id wf9mr37451531pbc.145.1447611977983; Sun, 15 Nov 2015 10:26:17 -0800 (PST) Received: from [192.168.20.7] (c-24-16-212-205.hsd1.wa.comcast.net. [24.16.212.205]) by smtp.gmail.com with ESMTPSA id iy1sm31693866pbb.85.2015.11.15.10.26.16 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 15 Nov 2015 10:26:16 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues? From: NGie Cooper In-Reply-To: <5648CBA1.9010300@freebsd.org> Date: Sun, 15 Nov 2015 10:26:15 -0800 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <2C639B6D-578D-4D23-8863-44F9DD74C693@gmail.com> References: <0650CA79-5711-44BF-AC3F-0C5C5B6E5BD9@rdsor.ro> <5648C964.2020405@freebsd.org> <2DF061E9-2541-4B10-9744-C49C515FF672@gmail.com> <5648CBA1.9010300@freebsd.org> To: Allan Jude X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 18:26:18 -0000 > On Nov 15, 2015, at 10:14, Allan Jude 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=