Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77506 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54707 invoked from network); 23 Sep 2014 07:38:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Sep 2014 07:38:40 -0000 Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.169 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 74.125.82.169 mail-we0-f169.google.com Received: from [74.125.82.169] ([74.125.82.169:44101] helo=mail-we0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 87/07-09206-E7321245 for ; Tue, 23 Sep 2014 03:38:39 -0400 Received: by mail-we0-f169.google.com with SMTP id k48so4126274wev.0 for ; Tue, 23 Sep 2014 00:38:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=XWtqfOZnA1NxtwR1y/D9+BLAdGacL2TvIU0GwU2FXHc=; b=Dogb7BXs/FwbT9VoDnDUOf9SdRfDl3hvl1qssu8CV3t7cAihX5XJcMb72or3M/fxUP m6qySwGyH6pMpuvAEoHRoIwawGkR15O+xl0rY1fjtw+7jYWgeLRlEU8kAqNUJZcdIJ3+ dLEQTcpVmtkJam9QkGS7RkzYzA7OCaSkKwTbY1LMI8kZvH02E17+SW7yTYVmo16/pV3J j+5wYtSAjrfYCmUNtcSnemt2uGsf3ytWcSPNH/extDB45l+2SmDHokW0QEnzPVc5DMZx WqdZ5iqNb4WeaKDX/0zjEk4SdZwsR0PD2jeR854hwI2N00HKp9seNxgKklt4GlsUKQFj kYxg== X-Received: by 10.194.77.111 with SMTP id r15mr26543263wjw.27.1411457915819; Tue, 23 Sep 2014 00:38:35 -0700 (PDT) Received: from [192.168.4.120] (178-18-170-101.customer.bnet.at. [178.18.170.101]) by mx.google.com with ESMTPSA id w10sm14891162wje.10.2014.09.23.00.38.34 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Sep 2014 00:38:35 -0700 (PDT) Sender: Michael Wallner Message-ID: <5421237A.8000707@php.net> Date: Tue, 23 Sep 2014 09:38:34 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: Kris Craig CC: Sanford Whiteman , PHP Internals References: <54212042.7060600@php.net> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Change checkdnsrr() $type argument behavior From: mike@php.net (Michael Wallner) On 2014-09-23 09:30, Kris Craig wrote: > > > On Tue, Sep 23, 2014 at 12:24 AM, Michael Wallner > wrote: > > On 2014-09-23 06:00, Sanford Whiteman wrote: > >> What would happen is it'd throw an E_DEPRECATED for at least the > remainder > >> of 5.x, then throw the usual E_WARNING for a missing argument > starting in > >> 7.x with no default. > > > > Sounds OK to me now that I've noticed this: > > > > https://bugs.php.net/bug.php?id=68081 > > > > Pretty sure that's a sane report, and it's enough to make me say > > checkdnsrr() doesn't work now at all. > > > Given that this function is over 16 years old [1] and guessing that it > was used as a simple kind of email domain verification, I think > checkdnsrr() works as expected [2], [3]. > > [1] http://marc.info/?l=php-internals&m=90222489331812&w=2 > [2] http://tools.ietf.org/html/rfc2821#section-5 > [3] http://tools.ietf.org/html/rfc5321#section-5.1 > > -- > Regards, > Mike > > > Except that it doesn't work as expected because most devs (including > myself) aren't readily familiar with posts from 1998. And even if that > were its purpose back then, that really has no relevance today, as the > purpose and identity of PHP itself has evolved drastically since then. > > If that really is a concern, though, then I would propose getting rid of > checkdnsrr() altogether (or making it an alias of checkmxrr()) and > creating a new general-purpose DNS lookup function that returns a > boolean. Of course, I really don't think that's necessary since this > stuff from 16 years ago doesn't have any meaningful bearing on how it's > being used today by modern PHP developers. Phew, "modern" or rather "unaware" or "uneager to research"? Anyway, I'm done with this topic; I don't see any reason for action, except maybe, improving related documentation. -- Regards, Mike