Assume Default Settings
I have been informed with some frequency some frequency that my PHP solutions "don't work", typically due to an abundance of E_NOTICE messages. I suggest the following settings be assumed by default:
short_open_tag = On
precision = 14
error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED
These are all default values, as they would be without a configuration file. For example, the following should be valid, even in challenges where producing any errors is prohibited:
<?for(;$i++<10;);
despite generating an E_NOTICE, due to accessing a previously undefined variable. This message is by default not displayed. On a similar note, suppressing errors with @ should also be allowed in these cases.
Assume Default Settings
I have been informed with some frequency that my PHP solutions "don't work", typically due to an abundance of E_NOTICE messages. I suggest the following settings be assumed by default:
short_open_tag = On
precision = 14
error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED
These are all default values, as they would be without a configuration file. For example, the following should be valid, even in challenges where producing any errors is prohibited:
<?for(;$i++<10;);
despite generating an E_NOTICE, due to accessing a previously undefined variable. This message is by default not displayed. On a similar note, suppressing errors with @ should also be allowed in these cases.
Assume Default Settings
I have been informed with some frequency that my PHP solutions "don't work", typically due to an abundance of E_NOTICE messages. I suggest the following settings be assumed by default:
short_open_tag = On
precision = 14
error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED
These are all default values, as they would be without a configuration file. For example, the following should be valid, even in challenges where producing any errors is prohibited:
<?for(;$i++<10;);
despite generating an E_NOTICE, due to accessing a previously undefined variable. This message is by default not displayed. On a similar note, suppressing errors with @ should also be allowed in these cases.
Assume Default Settings
I have been informed with some frequency that my PHP isn't exactly the most competitivie golfing languagesolutions "don't work", but I've done my best in the pasttypically due to give it fair representationan abundance of E_NOTICE messages. Whenever I post anything in PHP, I assumesuggest the followingphp.ini settings, without explicitly mentioning them be assumed by default:
short_open_tags = ondisplay_errors = stderr
short_open_tag = On
precision = 14
error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED
Routing warnings and errors to stdoutby default is perhaps one of the worst decisions ever made by any language development teamThese are all default values, everas they would be without a configuration file. Imagine, forFor example, an error message - displayed in the browser - detailing exactly which mysql function failedfollowing should be valid, and why. Brilliant.even in challenges where producing any errors is prohibited:
<?for(;$i++<10;);
Error messages haven't been disableddespite generating an E_NOTICE, they've just been re-routeddue to the proper channelaccessing a previously undefined variable. I think I have good precedent to assume this: both phpGolf and Anarchy Golf assume the same settingsThis message is by default not displayed. And for both sitesOn a similar note, suppressing errors with stderr@ is ignoredshould also be allowed in these cases.
PHP isn't exactly the most competitivie golfing language, but I've done my best in the past to give it fair representation. Whenever I post anything in PHP, I assume the followingphp.ini settings, without explicitly mentioning them:
short_open_tags = ondisplay_errors = stderr
Routing warnings and errors to stdoutby default is perhaps one of the worst decisions ever made by any language development team, ever. Imagine, for example, an error message - displayed in the browser - detailing exactly which mysql function failed, and why. Brilliant.
Error messages haven't been disabled, they've just been re-routed to the proper channel. I think I have good precedent to assume this: both phpGolf and Anarchy Golf assume the same settings. And for both sites, stderr is ignored.
Assume Default Settings
I have been informed with some frequency that my PHP solutions "don't work", typically due to an abundance of E_NOTICE messages. I suggest the following settings be assumed by default:
short_open_tag = On
precision = 14
error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED
These are all default values, as they would be without a configuration file. For example, the following should be valid, even in challenges where producing any errors is prohibited:
<?for(;$i++<10;);
despite generating an E_NOTICE, due to accessing a previously undefined variable. This message is by default not displayed. On a similar note, suppressing errors with @ should also be allowed in these cases.
PHP isn't exactly the most competitivie golfing language, but I've done my best in the past to give it fair representation. Whenever I post anything in PHP, I assume the following php.ini settings, without explicitly mentioning them:
short_open_tags = ondisplay_errors = stderr
Routing warnings and errors to stdout by default is perhaps one of the worst decisions ever made by any language development team, ever. Imagine, for example, an error message - displayed in the browser - detailing exactly which mysql function failed, and why. Brilliant.
Error messages haven't been disabled, they've just been re-routed to the proper channel. I think I have good precedent to assume this: both phpGolf and Anarchy Golf assume the same settings. And for both sites, stderr is ignored.