Thank you very much! Once I realized the source of the problem,
I was dismayed that one could declare a constant and have the
interpreter absolutely ignore it without warning. I already had
error_reporting to E_ALL in php.ini, so was unaware of what else
I could do. Didn't think to look for 'dis
On 24 June 2010 22:41, James Long wrote:
outputs ...
Notice: Constant LOG_WARNING already defined in - on line 4
LOG_NORMAL 0
LOG_WARNING 5
LOG_ERROR 2
I'm on Win32 PHP 5.3.3-RC1 (cli) (built: Jun 17 2010 22:43:29)
--
-
Richard Quadling
"Standing on the shoulders of some very clever
On 24/06/10 23:08, Ashley Sheridan wrote:
On Thu, 2010-06-24 at 23:02 +0100, Tim Schofield wrote:
Very strange, as
seems to work fine
Tim
It would, you misspelt LOG_WARNING with a lowercase 'i' ;)
Thanks,
Ash
http://www.ashleysheridan.co.uk
Thats what I was trying to illustrate, it
On Thu, 2010-06-24 at 23:02 +0100, Tim Schofield wrote:
> On 24/06/10 22:41, James Long wrote:
> > Perhaps I am missing something basic here.
> >
> > Why does the LOG_WARNING constant take on a value of 4, when
> > it is defined with a value of 1?
> >
> > Thank you!
> >
> > Jim
> >
> >
> > $ cat b
On 24/06/10 22:41, James Long wrote:
Perhaps I am missing something basic here.
Why does the LOG_WARNING constant take on a value of 4, when
it is defined with a value of 1?
Thank you!
Jim
$ cat bug.php
$ php bug.php
LOG_NORMAL 0
LOG_WARNING 4
LOG_ERROR 2
$
Very strange, as
seems to w
5 matches
Mail list logo
