Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.


Could you provide a screenshot that highlights the issue?

Bug seems to have been fixed - I can't see it anymore anyway, so this should just be closed

what he mean probably this.
http://php.net/operators.bitwise
http://pbs.twimg.com/media/BWHpBpkCEAAym94.png

even tough the upper part is mean to be an explanation,
some poeple think it as an example. all of them using
monospace font, so it is strange.

my propose is:
<!-- this use normal style -->
PHP's error_reporting ini setting uses bitwise values,
providing a real-world demonstration of turning
bits off. To show all errors, except for notices,
the php.ini file instructions say to use:
E_ALL & ~E_NOTICE

<!-- this use boxed monospace font, like the output
part at the bottom of the page -->
This works by starting with E_ALL:
00000000000000000111011111111111
Then taking the value of E_NOTICE...
00000000000000000000000000001000
... and inverting it via ~:
11111111111111111111111111110111
Finally, it uses AND (&) to find the bits turned
on in both values:
00000000000000000111011111110111

<!-- this use normal style -->
Another way to accomplish that is using XOR (^)
to find bits that are on in only one value or the other:
E_ALL ^ E_NOTICE
      
error_reporting can also be used to demonstrate turning bits on.
The way to show just errors and recoverable errors is:
E_ERROR | E_RECOVERABLE_ERROR

<!-- this use monospace font again -->      
This process combines E_ERROR
00000000000000000000000000000001
and
00000000000000000001000000000000
using the OR (|) operator
to get the bits turned on in either value:
00000000000000000001000000000001

No, the layout was decidedly broken - didn't check why but best guess was broken html. The examples were flowing together in a manner where you couldn't tell example and text apart.

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.