You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Kevin Brown (JIRA)" <ji...@apache.org> on 2008/03/07 13:11:46 UTC

[jira] Commented: (SHINDIG-114) _IG_Callback is not defined, need for legacy support

    [ https://issues.apache.org/jira/browse/SHINDIG-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576159#action_12576159 ] 

Kevin Brown commented on SHINDIG-114:
-------------------------------------

I can't find actual documentation for this function on igoogle. It seems like broken behavior to me:

Consider this:

function func(arg0, arg1) {
  alert(arg0 + arg1);
}

_IG_Callback(func, "world")("hello", "haha i broke your API");

vs

gadgets.util.makeClosure(null, func, "hello")("world", "haha i broke your API")

The second outputs 'world haha i broke your API' I can't reference my original data by name. This makes it impossible for callers to add new arguments in the future. 

The first outputs 'hello haha i broke your API world'

Is this true on igoogle today, or does it ensure a predictable signature by keeping the arguments in place?

> _IG_Callback is not defined, need for legacy support
> ----------------------------------------------------
>
>                 Key: SHINDIG-114
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-114
>             Project: Shindig
>          Issue Type: Bug
>          Components: Features
>            Reporter: Bruno Bowden
>            Assignee: Kevin Brown
>         Attachments: _IG_Callback-legacy.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.