Hi!
unqualified aliases, it would be useful to extend this functionality
to string references to these classes/functions/constants as well.
It would require to carry "namespace context" around with every
function/class in runtime and for me the usecase is not clear. Can you
describe more in
Hi!
I'd opt for option (d) for all prototype/signature checking. Here's why:
I think relaxing the check may make sense. Do you have some code example
that doesn't work and you want it to work?
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 22
On Thu, 05 Aug 2010 14:54:21 +0100, Gustavo Lopes
wrote:
Hi
I've modified Closure::bindTo/Closure::bindTo so that they accept another
argument that defines the new scope. This can either be an object (its
class is used as the scope) or a class name.
[...]
Sending renamed attachments.
--
G
Hi
I've modified Closure::bindTo/Closure::bindTo so that they accept another
argument that defines the new scope. This can either be an object (its
class is used as the scope) or a class name.
I changed the current behavior so that:
* If the scope is not given, the current one is kept. Thi
