Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108680 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 18011 invoked from network); 19 Feb 2020 19:19:50 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 19 Feb 2020 19:19:50 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 3737C18054E for ; Wed, 19 Feb 2020 09:35:48 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-io1-f50.google.com (mail-io1-f50.google.com [209.85.166.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 19 Feb 2020 09:35:47 -0800 (PST) Received: by mail-io1-f50.google.com with SMTP id t26so1423294ioi.13 for ; Wed, 19 Feb 2020 09:35:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=R0hlxm4Jo7X18LS7cWo55v0lE02UC7de2qk2miHNRGY=; b=G+0gAOQcIPzFJZ3r6B8yVuTDie1Or32Vocjq7BxNCIdtauyH6YuZLqdZFqXyDE2xV0 R7VxAPkwpvk5HTiPOfJQiKTrBchZiU+5t8FQbtHeoVssSgphFK4OZb367dZcxHi/JyVX mdJ6/+CrgnwE/qiXDlxBCpuB+S9ZpPJ9IYweYG8EJpeYyWs6W7G6YR9AsLdQUlsJLm4e CW/6+l4wq8AKEe9YgYK6AdYsYKSXIV89hDjFlajGLMsUUGbCR4I5GwN2tzXmMMf4YBEL dbHVKD5M9XbeiI6tJQ80AtDdXx+is1DpAXqa7oMfISTgN+fi3whbhjsfG/gbDPNxkHTK WTzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=R0hlxm4Jo7X18LS7cWo55v0lE02UC7de2qk2miHNRGY=; b=k75bjNFx46pZoyGpW+B160rh8Eg+WLgnIeTwoEHCFw1LD2vpUB0LNXjbeX5fFPjR/h g/QB9LpbnnanqbjzWeeCAYkf6iYbycLuhfA+D+v1c45iJblXghkTkfOSj1rR9BMQcgdS nWtwteMb6FHZhkpsdhsSQdpCIJ/o+ld/9PgAvZaDexva2pkn7oIJc33FhuOTgVSJK47b DJxCpsZHO7fhuvr7tiRnIGUvwIc9Zk3vGRTflSo5S7Ka1MGCZ1uPTFf8mBNbpINdwId5 zWXwg46E1mVA+khxbxH+92m1ZvV/pqP1Sp0kFI4o2Xxe1guwUrL0xqwja+vwkNmyza0p rtRg== X-Gm-Message-State: APjAAAXWSOh8L2/oaLzQnEvgrPAQtVKGxTAIfNuEIL/iWotDgJU5h0jk ysTJmHp33/cArgvfNCYqtajKFDpjI28LffN/1McGlA8W X-Google-Smtp-Source: APXvYqxsP9+/g5YLbWTH2cj80zRyRO3erQrgmYUCy0Fa0om/SkljJ5U5WOfQ7Me1D5SgKq8zzJpsy2lYHQHcvHfT5ug= X-Received: by 2002:a05:6638:5b1:: with SMTP id b17mr21850459jar.66.1582133744643; Wed, 19 Feb 2020 09:35:44 -0800 (PST) MIME-Version: 1.0 References: <1586E4D0-B327-46A1-92C3-F9E2F89E33DB@newclarity.net> In-Reply-To: <1586E4D0-B327-46A1-92C3-F9E2F89E33DB@newclarity.net> Date: Wed, 19 Feb 2020 17:35:33 +0000 Message-ID: To: PHP Internals Content-Type: multipart/alternative; boundary="000000000000d65106059ef13775" Subject: Re: [PHP-DEV] New PCRE function From: rowan.collins@gmail.com (Rowan Tommins) --000000000000d65106059ef13775 Content-Type: text/plain; charset="UTF-8" On Wed, 19 Feb 2020 at 17:15, Mike Schinkel wrote: > From https://github.com/golang/go/wiki/CodeReviewComments#error-strings > > "Error strings should not be capitalized (unless beginning with proper > nouns or acronyms) or end with punctuation, since they are usually printed > following other context. That is, use fmt.Errorf("something bad") not > fmt.Errorf("Something bad"), so that log.Printf("Reading %s: %v", filename, > err) formats without a spurious capital letter mid-message. This does not > apply to logging, which is implicitly line-oriented and not combined inside > other messages." > Thanks, I can see the reasoning, although I'm not sure I agree with it. If you're only showing it to a programmer, worrying about the grammar of a capital letter after a colon seems needlessly pedantic. If you're showing it to end-users, you should probably be thinking about i18n anyway, and can load your own English translations (and user-friendly summaries) for whatever context you want to show them in. Regards, -- Rowan Tommins [IMSoP] --000000000000d65106059ef13775--