Description:
------------
I'd like common library writing were as clean as possible regarding includes. The problem is that "files for including are first looked in include_path relative to the current working directory and then in the directory of the current script", and not the other way round, thus forcing the programmer to write a dirty absolute path, which attemtpts against maintainability.

A possible solution would be that if the include argument starts with a dot (.), then maintain current behaviour, else, look in script's directory first.

Reproduce code:
---------------
File /test.php (run this):
<?php
include('lib/test2.php');
echo "/test.php<br>";
?>
---------------

File /lib/test2.php:
<?php
include('test.php'); //Intends to include /lib/test but includes /test.php
echo "/lib/test2.php<br>";
?>
---------------

File /lib/test.php:
<?php
echo "/lib/test.php<br>";
?>

Expected result:
----------------
/lib/test.php
/lib/test2.php
/test.php

Actual result:
--------------
Fatal error: Maximum function nesting level of '100' reached, aborting! /lib/test2.php on line 2