Re: Declare minimum PHP version required?
| From: | Lester Caine | Date: | Wed, 05 Feb 2014 10:45:50 +0000 |
| Subject: | Re: Declare minimum PHP version required? | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-72260@lists.php.net to get a copy of this message | ||
Pierre Joye wrote:
On Wed, Feb 5, 2014 at 11:03 AM, Lester Caine<lester@lsces.co.uk> wrote: Yasuo Ohgaki wrote: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.ukYasuo 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.Yes. New assert() is as efficient as declare(). I cannot wait to use new assert()!