Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <6971699.1168849587879.JavaMail.jira@brutus>
Date: Mon, 15 Jan 2007 00:26:27 -0800 (PST)
From: "Mark Lundquist (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Subject: [jira] Commented: (COCOON-1981) Allow <map:call> to call any
 function
In-Reply-To: <843240.1168849108067.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COCOON-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464680 ] 

Mark Lundquist commented on COCOON-1981:
----------------------------------------

Please delete the first two of the three attached files.  The first one was too big a diff and included unrelated changes to a different file.  The second is identical (botched attempt to correct the first).

The third file is the good patch file.


> Allow <map:call> to call any function
> -------------------------------------
>
>                 Key: COCOON-1981
>                 URL: https://issues.apache.org/jira/browse/COCOON-1981
>             Project: Cocoon
>          Issue Type: Improvement
>          Components: - Flowscript
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Mark Lundquist
>            Priority: Minor
>         Attachments: 1981.patch, 1981.patch, 1981.patch
>
>
> Currently, <map:call> can only call a function that is a property of the flowscript global scope itself.  This patch allows it to call any function in the global scope, e.g. "foo.bar.baz".
> I provided this code change originally to Jeremy Quinn who committed it to BRANCH_2_1_X, but it has not yet been incorporated into trunk.
> The only additional thing I would suggest... would it be worth it to test if funName.contains ("."), and if so look up the function the old way?  Don't know if that's significantly faster...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira