# php.ini-dist - Thread: https://externals.io/message/9371 - Original archive: https://news-web.php.net/php.internals/9371 - Started by Kenneth Schwartz on 2004-04-19T10:30:08+00:00 - Messages: 8 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #9371 — Kenneth Schwartz — 2004-04-19T10:30:08+00:00 URL: https://externals.io/message/9371#9371 php.ini-dist in HEAD has the following value: error_reporting = `E_ALL` & ~E_NOTICE & ~E_STRICT It's odd that `E_STRICT` is explicitly excluded as `E_ALL` does not include it. Is there a purpose to it? Perhaps it's something I don't know about ;) Kenneth --- ## #9373 — Andi Gutmans — 2004-04-19T10:46:41+00:00 URL: https://externals.io/message/9371#9373 · In reply to: #9371 I guess it's just verbosity. At 06:30 AM 4/19/2004 -0400, Kenneth Schwartz wrote: >php.ini-dist in HEAD has the following value: > >error_reporting = `E_ALL` & ~E_NOTICE & ~E_STRICT > >It's odd that `E_STRICT` is explicitly excluded as `E_ALL` does not include >it. Is there a purpose to it? Perhaps it's something I don't know >about ;) > >Kenneth --- ## #9372 — Derick Rethans — 2004-04-19T10:46:44+00:00 URL: https://externals.io/message/9371#9372 · In reply to: #9371 > php.ini-dist in HEAD has the following value: > > error_reporting = `E_ALL` & ~E_NOTICE & ~E_STRICT > > It's odd that `E_STRICT` is explicitly excluded as `E_ALL` does not include > it. Is there a purpose to it? Perhaps it's something I don't know > about ;) Needs fixing, the & ~E_STRICT part should go out. Derick --- ## #9392 — Marcus Boerger — 2004-04-19T18:51:57+00:00 URL: https://externals.io/message/9371#9392 · In reply to: #9372 Hello Derick, i think we should leave it in because we might remove it from `E_ALL` in later php versions. marcus Monday, April 19, 2004, 12:46:44 PM, you wrote: > > > […] > Needs fixing, the & ~E_STRICT part should go out. > Derick -- Best regards, Marcus mailto:helly@php.net --- ## #9393 — Derick Rethans — 2004-04-19T19:01:35+00:00 URL: https://externals.io/message/9371#9393 · In reply to: #9392 > i think we should leave it in because we might remove it from `E_ALL` in later > php versions. Uh? `E_STRICT` is not part of E_ALL, but in case you meant it the other way around I agree, let's leave it there :) Derick --- ## #9394 — Marcus Boerger — 2004-04-19T19:02:00+00:00 URL: https://externals.io/message/9371#9394 · In reply to: #9392 > Hello Derick, > i think we should leave it in because we might remove it from `E_ALL` in later > php versions. Erm i meant we may add `E_STRICT` to `E_ALL` in a later version. > marcus > Monday, April 19, 2004, 12:46:44 PM, you wrote: > > […] > > […] > > […] > > […] > -- > Best regards, > Marcus mailto:helly@php.net -- Best regards, Marcus mailto:helly@php.net --- ## #9398 — Christian Schneider — 2004-04-19T21:29:07+00:00 URL: https://externals.io/message/9371#9398 · In reply to: #9394 Marcus Boerger wrote: > Erm i meant we may add `E_STRICT` to `E_ALL` in a later version. ... which would be a big BC break. Remember that 'var' produces a warning under E_STRICT. And 'var' is here to stay for a *long* time. - Chris --- ## #9399 — Marcus Boerger — 2004-04-19T21:33:02+00:00 URL: https://externals.io/message/9371#9399 · In reply to: #9398 Hello Christian, then obviously `E_STRICT` must stay out of `E_ALL` for long time. Still explicitly showing there's more is a good thing. Maybe some text near the setting would be good. marcus Monday, April 19, 2004, 11:29:07 PM, you wrote: > Marcus Boerger wrote: > > […] > ... which would be a big BC break. Remember that 'var' produces a > warning under E_STRICT. And 'var' is here to stay for a *long* time. > - Chris -- Best regards, Marcus mailto:helly@php.net