Bug #15523 Updated: Line Number

ID: 15523 Updated by: bigredlinux@yahoo.com Reported By: blanke@ddd.de Status: Open Bug Type: Feature/Change Request Operating System: Linux PHP Version: 4.1.1 New Comment: What would be nice is if line() and file() were functions and they returned an array of line numbers and files...Hence, for each level of depth you proceed, it would array_push the line and file and then when you exited it would pop them. That way, you could get the whole hierarchy, and without and punishment. I realize that php is going towards stack tracing, but this would be HUGE. PEAR_Error would actually be helpful in cases that used this functionality. Previous Comments: ------------------------------------------------------------------------ [2002-02-12 10:53:00] jan@php.net reopening, this is a serious request ;) ------------------------------------------------------------------------ [2002-02-12 10:51:37] blanke@ddd.de That would work of course. The problem is, that our company has written a set of php functions, which are used by one of our clients. The functions include some error-handling like wrong arguments or something like that, and I'd like to tell them the linenumber. I think its not very useful that they have to put __LINE__ into every function call :) ------------------------------------------------------------------------ [2002-02-12 10:47:52] jan@php.net what about function foo($line) { echo 'the function was called in line: '.$line } foo(__LINE__); ? ------------------------------------------------------------------------ [2002-02-12 10:45:32] blanke@ddd.de Hi there! That's correct, that __LINE__ contains the !current! Line-Number. But I what to know from which line a function has been called. > > > > 1 function blah() > > 2 { > > 3 echo("Function blah has been called from line 6"); > > 4 } > > 5 > > 6 blah(); > > In line 3, i don't want to know the CURRENT line Number. I'd like to know the Line-Number from which that Function has been called. mfg, Nico Blanke. ------------------------------------------------------------------------ [2002-02-12 10:40:45] jan@php.net in fact it is bogus ;) ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/15523 -- Edit this bug report at http://bugs.php.net/?id=15523&edit=1