You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Mark Lundquist (JIRA)" <ji...@apache.org> on 2007/01/15 09:18:28 UTC
[jira] Created: (COCOON-1981) Allow to call any function
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
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
[jira] Commented: (COCOON-1981) Allow to call any
function
Posted by "Mark Lundquist (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (COCOON-1981) Allow to call any function
Posted by "Jörg Heinicke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COCOON-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jörg Heinicke updated COCOON-1981:
----------------------------------
Attachment: (was: 1981.patch)
> 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
>
>
> 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
[jira] Updated: (COCOON-1981) Allow to call any function
Posted by "Mark Lundquist (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COCOON-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Lundquist updated COCOON-1981:
-----------------------------------
Attachment: 1981.patch
> 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
>
>
> 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
[jira] Closed: (COCOON-1981) Allow to call any function
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COCOON-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed COCOON-1981.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.2-dev (Current SVN)
Patch applied. Thanks!
> 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
> Fix For: 2.2-dev (Current SVN)
>
> Attachments: 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
[jira] Updated: (COCOON-1981) Allow to call any function
Posted by "Mark Lundquist (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COCOON-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Lundquist updated COCOON-1981:
-----------------------------------
Attachment: 1981.patch
> 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
>
>
> 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
[jira] Updated: (COCOON-1981) Allow to call any function
Posted by "Mark Lundquist (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COCOON-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Lundquist updated COCOON-1981:
-----------------------------------
Attachment: 1981.patch
> 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