On Wed, Feb 5, 2014 at 11:03 AM, Lester Caine<
[email protected]> 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.