Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72260
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.204 cause and error)
Message-ID: <52F2165E.6040104@lsces.co.uk>
Date: Wed, 05 Feb 2014 10:45:50 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <CAGa2bXYHP5D70bDBhbWzE7-B0s2kgk7DmAZdFhXkLqMJQqKV5g@mail.gmail.com>	<52EF4BF8.60005@sugarcrm.com>	<CAGa2bXacCxnmcAPZjh-YgTNocMjEpu_Uoc4npfNcKVM2WA2Tow@mail.gmail.com>	<CAGa2bXZt7n8aqA=VrBKsqBzFiusGZP7aECPO-7xQher4+uVLWg@mail.gmail.com>	<52F14C66.3030806@gmail.com>	<CAH-PCH4+ULN2bVh=A2ZNvXmpYDqBPA3JrhhdrKb5zVH_sXucxg@mail.gmail.com>	<52F15B62.1070006@gmail.com>	<CAH-PCH4qXWJF_qN2ap0u+ufOMTah3VTR9t-BrV+9qkqD-KdixQ@mail.gmail.com>	<CAGa2bXaj3Az2yYswgpS1yTFiYR+=j2tM-5y5paMrcjftx=X9pw@mail.gmail.com>	<52F20C7C.3040803@lsces.co.uk> <CAEZPtU5OPzcOmXbY2mgHr7Ckz=k852DXsf3pNg9Ut5qVv07qbA@mail.gmail.com>
In-Reply-To: <CAEZPtU5OPzcOmXbY2mgHr7Ckz=k852DXsf3pNg9Ut5qVv07qbA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Declare minimum PHP version required?
From: lester@lsces.co.uk (Lester Caine)

Pierre Joye wrote:
> On Wed, Feb 5, 2014 at 11:03 AM, Lester Caine<lester@lsces.co.uk>  wrote:
>> >Yasuo Ohgaki wrote:
>>> >>
>>> >>Yes. New assert() is as efficient as declare().
>>> >>I cannot wait to use new assert()!
>> >
>> >
>> >Yasuo
>> >Please can you explain why you think this is so essential? The only place I
>> >can think that I would use this I ALSO need to advise the users that there
>> >is a problem. Adding 'assert' which apparently only has use while debugging
>> >just seems wrong. Alright I add vd() and similar myself when debugging code
>> >rather than using a 'debugger', but if I need to test something only at
>> >debug time then I'll just add code and remove it when I have sorted the
>> >problem. If it is a problem which will stop the code running, then it needs
>> >a proper response in the workflow anyway.
>> >
>> >ADOdb and smarty both have switches to enable debugging which can be
>> >switched on as required at runtime and I can't see any reason they would
>> >switch to using assert instead?
> Let me rephrase that in another way.
>
> It is no rocket science to correctly setup a production server.
> Disable display errors, eanble log, create error pages (404, etc.).
> Anyone not being able to understand or able to actually do it has
> nothing to do anywhere closed to a production server.

Pierre - now you have lost me totally ...
What does this have to do with 'assert' ?
I'm quite happy to put my hands up and say "I don't understand why it's needed"

If you look at the bulk of PHP users, they are using PHP via a hosting service, 
who set up the 'production server' for them. When they install an 'application', 
it's install section takes care of configuration. Then the ISP changes PHP 
version and they get a white screen ... help ...

At this point what PHP needs to supply as a minimum is just a 'php has crashed 
please check log', but ideally we should be able to direct these 'simple' users 
back to their installation section if that can handle the problem. 95% of users 
would probably not understand what the difference between a production and 
develop server is? Telling them they have no place using PHP is not acceptable?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk