Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108625 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 56872 invoked from network); 17 Feb 2020 01:09:43 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 17 Feb 2020 01:09:43 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id C59931804AB for ; Sun, 16 Feb 2020 15:24:58 -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=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, SPF_HELO_NONE,SPF_NONE 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-yw1-f68.google.com (mail-yw1-f68.google.com [209.85.161.68]) (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 ; Sun, 16 Feb 2020 15:24:58 -0800 (PST) Received: by mail-yw1-f68.google.com with SMTP id h126so7100506ywc.6 for ; Sun, 16 Feb 2020 15:24:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=newclarity-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zigPBd1Lkxv+CBuYOJqjJsgeMd/LdCYwrza01zTpEGc=; b=Im6/gW9+1d0wS3UpOt8dyxr7gD30y5lTNH7If+8KmfaRq4KZFHNJfjvZXapEuBMYMs deAza65gcHwlZ4w6+yffEcj9+5tIN9aiQe0Ws+mvF8RSvoMjyz9eWUkeSEUjhLBcgE6e Inv88jBHiX6RLJO91XIrVR6jTgKqSnjgZdZi/zxi4K3+tISrGLZJRMBu1weRbXXo1N6c SsD7u55YdOMl95Ci6xbGDfsWw1CIkBj4Yt3xP4WkWU8+zzERtcoOl4Ic2HvCOLhvYE/Y FJfJXRteodcdk1FPZEgT591y+uqEiKcFDHgYRihMBxSiJfhv0ghBpzD+0PDo1GW4xyXS JZBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zigPBd1Lkxv+CBuYOJqjJsgeMd/LdCYwrza01zTpEGc=; b=DY5ZI4YM5B6OpQc6zJvxlrnAQywlTIwuhRFIXy9nR5zZfNFKUqii9FXclLUD9ZdY2L nAqW4Twqjibluiz4nrI354JVmdVG7DQgK9nWYu00eFI96qrvHwHJfTCbTku2Lg6Io+VL woXYW5nMik2emqV7stnYvVOAKYRW3WPhT9+Gr+UuAtlqTc2DHB23D9JNglYXwO+t77Uk uqJbs3YQDC2C7fqwYulWt/j7da6Rgqt7iaQAR6/xlkAHCN2Vwiq1YlOB+BOQugbGzGqh EhfERmfKh/m56oZuLIF3VWmU+5FOMCwNFX0wFAakFpPAgpk5IvibV2pjOMQl9JDKyEXN xDOw== X-Gm-Message-State: APjAAAVG/bwU9OqDPr43dRlKMBDf/5/RFre0JwRbupaLyMvNYaBdnbS+ 5n52onlsnScSNtIXZ1M6xQnRGQ== X-Google-Smtp-Source: APXvYqz9QTQV1/Ikt1vryw+g8LOOGggHvTUVob5ldedhjInzJ5rkZ3f+tdVnav6ldimKZhLEIYTUag== X-Received: by 2002:a81:3e25:: with SMTP id l37mr11050990ywa.212.1581895497573; Sun, 16 Feb 2020 15:24:57 -0800 (PST) Received: from ?IPv6:2601:c0:c680:5cc0:10bb:4bd6:7ac1:f816? ([2601:c0:c680:5cc0:10bb:4bd6:7ac1:f816]) by smtp.gmail.com with ESMTPSA id g128sm5581920ywb.33.2020.02.16.15.24.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 16 Feb 2020 15:24:57 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) In-Reply-To: <5e494067.1c69fb81.b045d.d4e7SMTPIN_ADDED_MISSING@mx.google.com> Date: Sun, 16 Feb 2020 18:24:56 -0500 Cc: internals@lists.php.net Content-Transfer-Encoding: quoted-printable Message-ID: References: <0C8F7155-8F2E-4999-8C01-995203535001@newclarity.net> <5e494067.1c69fb81.b045d.d4e7SMTPIN_ADDED_MISSING@mx.google.com> To: Mark Randall X-Mailer: Apple Mail (2.3445.104.11) Subject: Re: [PHP-DEV] [RFC] get_debug_type From: mike@newclarity.net (Mike Schinkel) > On Feb 16, 2020, at 8:15 AM, Mark Randall wrote: >=20 > On 16/02/2020 10:16, Mike Schinkel wrote: >> Why "debug" type? >=20 > I would imagine because it is only really useful in the context of = debugging.=20 JMTCW but I generally think names should describe what something is, not = what it can be used for. The former can typically be definitive, the = latter is based on perspective and thus both multiple names could apply = and for some people the "can be used for" name turns out to be = confusing.=20 For example, when I first saw the name I was wondering if it would = return some kind of debugging "mode" and was curious if there were more = than one mode for debugging. I was hopeful that there was something new = about debugging for me to learn.=20 > There is no reason to ever expose such information to userland. Hmm. Depending on what you envision, I could definitely see using it in = userland. Basically something that merges gettype() and get_class() so = that I can get one definitive type for a value and not have to call two = functions. I can of course write my own, but my own would not be = "standard" and so I would see value in having a standard function for = this in core. > The name is up for debate. Cool. =20 Though still not exactly sure where you are headed with it since there = are few detailed and no code examples the first name that comes to mind = for me would be get_real_type(). -Mike=