On Tue, Sep 29, 2009 at 4:14 PM, brian wrote:
>
> On Tue, Sep 29, 2009 at 2:19 AM, Bert Van den Brande
> wrote:
> > Ok tnx now I understand the problem, though I still can't wrap my head
> > around the core issue.
> >
> > Is it that call_user_func_array() can never call private methods ? I
> fou
On Tue, Sep 29, 2009 at 2:19 AM, Bert Van den Brande wrote:
> Ok tnx now I understand the problem, though I still can't wrap my head
> around the core issue.
>
> Is it that call_user_func_array() can never call private methods ? I found
> some comments here and there on the web stating that the n
Ok tnx now I understand the problem, though I still can't wrap my head
around the core issue.
Is it that call_user_func_array() can never call private methods ? I found
some comments here and there on the web stating that the new Reflection API
will solve this, but nothing concrete on calling priv
On Mon, Sep 28, 2009 at 11:20 AM, Bert Van den Brande wrote:
> I don't entirely understand why moving the target action from private to
> protected or public results in the $viewVars being set or not set ?
The first line in setAction() changes the controller's $action:
$this->action = $action;
I don't entirely understand why moving the target action from private to
protected or public results in the $viewVars being set or not set ?
On Mon, Sep 28, 2009 at 5:05 PM, brian wrote:
>
> OK, I suppose that wasn't very clear. What I was getting at is that,
> if calling setAction(), the target
OK, I suppose that wasn't very clear. What I was getting at is that,
if calling setAction(), the target action must have either public or
protected access.
On Sun, Sep 27, 2009 at 11:20 PM, Martin Radosta
wrote:
>
> On 09/27/2009 04:31 PM, brian wrote:
>> The comment for setAction() says that it
On 09/27/2009 04:31 PM, brian wrote:
> The comment for setAction() says that it "Internally redirects one
> action to another." However, it doesn't really *redirect* so much as
> simply call the action using call_user_func_array(). It amounts to
> about the same thing, more or less, but there's so
The comment for setAction() says that it "Internally redirects one
action to another." However, it doesn't really *redirect* so much as
simply call the action using call_user_func_array(). It amounts to
about the same thing, more or less, but there's something to keep in
mind:
public function som
