Actually, it should allow for returning *why* the parsing failed as well. Assigning to myself.

I did a quick and dirty patch to turn the $component into a bitfield
allowing you to do:
$url = parse_url('http://www.php.net/manual/', PHP_URL_HOST | PHP_URL_PATH);
printf('%s%s', $url['host'], $url['path']);

At the same point I figured we could disable the warning and therefore
I added a new constant named PHP_URL_SILENT:
$broken_url = 'http:///www.php.net/';
var_dump(parse_url($broken_url), parse_url($broken_url, PHP_URL_SILENT));

It doesn't alter the actual URL parser code to tell why the parsing
failed, but it kills two flies in one hit. Ofcourse the silent option
can be skipped, but while atleast updating parse_url().

The patch uploaded here does not currently fix any broken tests.

Theres a minor BC break, since it changes the values of the constants,
but it can be fixed by changing the checking code, or the dirty way to
increase the values so they don't conflict with the old ones.

Derick, I don't see why you would change the return value here. Please explain your reasoning.

However the patch to remove the warning can be applied already, as I explained on internals.

I don't think the bit fields should be used to hide the warning.

This is STILL throwing E_WARNING.  Not good.

It does not, as of PHP 5.3.3.