Fix documentation of security callbacks.

Actually 1st parameter could be any object in prototype chain from this to actual holder, not only a
the global object.


git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2937 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
This commit is contained in:
antonm@chromium.org 2009-09-18 12:18:08 +00:00
parent 9b4c950963
commit a0bf4c55c4

View File

@ -1546,9 +1546,9 @@ enum AccessType {
/**
* Returns true if cross-context access should be allowed to the named
* property with the given key on the global object.
* property with the given key on the host object.
*/
typedef bool (*NamedSecurityCallback)(Local<Object> global,
typedef bool (*NamedSecurityCallback)(Local<Object> host,
Local<Value> key,
AccessType type,
Local<Value> data);
@ -1556,9 +1556,9 @@ typedef bool (*NamedSecurityCallback)(Local<Object> global,
/**
* Returns true if cross-context access should be allowed to the indexed
* property with the given index on the global object.
* property with the given index on the host object.
*/
typedef bool (*IndexedSecurityCallback)(Local<Object> global,
typedef bool (*IndexedSecurityCallback)(Local<Object> host,
uint32_t index,
AccessType type,
Local<Value> data);