On Thu, Aug 20, 2009 at 08:13, Lars Torben Wilson<larstor...@gmail.com> wrote: > Hi all, > > Just asking because I've been out of the loop for a while (again) but > a coworker recently noticed this BC break in func_get_args() and > friends. While the changes to way func_get_args() do seem necessary > this should probably still be documented. I just wanted to make sure > I'm not breaking any current standards too badly with this. :) > > I've added similar notes and examples to func-get-arg.xml and > func-arg-num.xml but have left them out of this email for brevity. > > If I don't hear any objections I'll commit tomorrow. Or if I get an OK > tonight, I'll commit tonight. :)
In 2 years (when everyone knows about the warning) people will be wondering why the example shows a complicated way to throw an error.. The example is nice to show what exactly no longer works, but the wording and example show a hint of disappointment that it doesn't work in 5.3.. I don't know how to rephrase it though ;) Maybe add <refsect role="errors">, including a file calling func_get_args() will throw an E_WARNING, even when included from functions.. ? -Hannes
