Description:
------------
[Exactly as per #17904. I am unable to re-open or add a comment to a 'bogus' report, and was told it would be best just to open a new bug report. See #17904 for background and a 'reproduce code' section. The following is the comment I would like to have added to the original report regarding the issue.]

I agree with David - it should be reporting the calling line number, so the developer can fix it the caller, not the line of the callee (the function definition) of which there is nothing wrong.

I have to disagree with Derrick's comments when closing this report. Normal developers shouldn't have to install third-party libraries or write their own stacktrace code just to find out where they're calling their own functions incorrectly! It's annoyed the hell out of me (and others I know who uses PHP) for years now, and I *really* can't believe (having just found out today) that this is considered 'expected behaviour' and a 'bogus' bug report! Derrick, are you sure?

Any chance we could get this re-opened and/or fixed properly?

Thanks.


Expected result:
----------------
The 'missing argument' warning/error should report the line number of the caller, not the function