Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101468 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87063 invoked from network); 1 Jan 2018 09:12:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jan 2018 09:12:18 -0000 X-Host-Fingerprint: 62.31.75.76 76.75-31-62.static.virginmediabusiness.co.uk Received: from [62.31.75.76] ([62.31.75.76:19354] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9F/00-18298-07BF94A5 for ; Mon, 01 Jan 2018 04:12:18 -0500 Message-ID: <9F.00.18298.07BF94A5@pb1.pair.com> To: internals@lists.php.net References: <72392123-d37b-26df-6886-218f48205f8a@fleshgrinder.com> <58A5ABDF-AA25-46D4-83E7-4DE72E3DFF5E@gmail.com> <757270790.33iDQ9MZ2V@vulcan> <4b55eed1-8656-ff70-e4e9-ad5e40213405@rhsoft.net> <73.EE.47595.179574A5@pb1.pair.com> <50caeb2d-62b6-167d-726e-e0e11ea201f3@lsces.co.uk> <28ba9e6a-a3f2-2547-d294-f3a1710d5337@rhsoft.net> <14.A3.47595.2FAB84A5@pb1.pair.com> <7482b9d4-d487-8c0f-1f92-2e8fef68d2ed@rhsoft.net> In-Reply-To: <7482b9d4-d487-8c0f-1f92-2e8fef68d2ed@rhsoft.net> Date: Mon, 1 Jan 2018 09:12:09 -0000 Lines: 6 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Newsreader: Microsoft Windows Live Mail 16.4.3564.1216 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216 X-Posted-By: 62.31.75.76 Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Scalar Pseudo-type From: TonyMarston@hotmail.com ("Tony Marston") wrote in message news:7482b9d4-d487-8c0f-1f92-2e8fef68d2ed@rhsoft.net... > > > >Am 31.12.2017 um 11:24 schrieb Tony Marston: >> Some of us are clever enough to write code that doesn't have those types >> of bug in the first place. I developed my framework in PHP4 before type >> hints even existed, and I developed a large enterprise application with >> that framework which is now being sold to large corporations all over the >> world. That codebase has moved from PHP 4 through all versions of PHP 5 >> and is now running on PHP 7.1. During these upgrades I have only changed >> my code to deal with what has been deprecated, and I have never bothered >> with any of those new optional extras (such as typehints) unless I have >> been convinced that the effort of changing my code has measureable >> benefits. > >well my codebase dates back to 2002 but is stricted-typed in the meantime - >and now? PHP was never strictly typed from the start, and I have always loved the flexibility that this provided. I have never felt the urge to use typehints (or type enforcement that it has now become)and any potential bugs that this may create are quickly identified and resolved during my testing. >> The idea that typehints provide benefits to the whole PHP community is >> completely bogus. It only provides apparent benefits to those programmers >> who have moved from a strictly type language to PHP and who feel lost >> without the crutch that a strongly typed language seems to provide. I >> work faster with a dynamically and weakly typed language, so speed of >> development is far more important to me. Any so-called bugs are detected >> and fixed during the testing phase, so I don't want the language being >> slowed down performing checks that I don't want. > >nosense - after 15 years PHP andmoved everything to strict_types in 2017 >(the current year) you can't accuse me that i have recebtly moved from a >strongly typed language to PHP and felt lost all the years before Just because a whole load of new features have been added to the language does not mean that I should use them. They are entirely optional, and I choose NOT to use them unless I am convinced that the benefits are worth the effort. >you think you work faster because you even don't realize small bugs until >they become large enough that you sit there and debug for hours while a >type-error with a stacktrace would have shown the mistake at the begin >including the root cause As I said previously, any such errors that may be caused by not using a strictly typed language are detected and fixed when I test my code. My main application has been in live use since 2008, and you can count on one hand the number of bugs which are reported each year. -- Tony Marston