|
Sept. 18, 2001 In This Issue
DevSpace
Developer Support Download Center |
One of the most useful and important features of the ScriptEase ISDK has long been the ability to wrap C/C++ objects automatically within JavaScript objects through the use of wrappers, dynamic callbacks, and various flags. In this way a C/C++ object can be represented transparently as a JavaScript object, and vice versa. C++ developers often ask for help with wrapping C++ objects as JavaScript objects. Now that help is available in the form of a C++ class: SEObjectWrapper. SEObjectWrapper Goals From the SEObjectWrapper Addendum:
SEObjectWrapper Manual
SEObjectWrapper is not the only way to integrate C++ classes with ISDK/C, and many of you will continue with your own methods that may best suit your applications. Whether you use SEObjectWrapper directly or only for ideas, I hope SEObjectWrapper proves useful in your ScriptEase development efforts. Have a question about how to use ScriptEase:ISDK? Let Dr. Scripter know at http://support.nombasxxx.com/ |
Introducing
SEObjectWrapper - Integrating C++ Objects with ScriptEase
Complete
documentation for SEObjectWrapper is available as an addendum
to the ISDK User Manuals, as the document: Errata
ISDK/C 4.30d
- get callback may crash during seobjHasProperty(): dynamic get callback crash when called during seobjHasProperty() to determine if the propery exists. [details]
- rare GC problem on dynamic objects: In very rare circumstances, a garbage-collection may occur during manipulation of a dynamic object callback that could invalidate an internal stack variable. This has never been found to happen in the field, but new internal debugging code has detected the possibility. [details]
- toString on functions concatenates some identifiers: When a function is being converted to a string, a required space may not be displayed after some variables. For example, "for(var foo in goo)" may become "for(var fooin goo)". [details]
- buffer.getString not stopping at the null character: Buffer.prototype.getString() is not terminating strings at the first null character, as specified in the documentation. [details]
- COMOBJ error on put: "object no longer connected": Under certain circumstances a call to comobj to put a value into a COM variable would either fail with an error saying that the object was no longer connected to the server or would crash ScriptEase outright. [details]
- VT_ARRAY has been added to COMOBJ: Update: VT_ARRAY has been added to COMOBJ for getters (although not yet for putters). This allows scripts interacting with COM objects to retrieve array data. [details]
ISDK/C 4.40c
- get callback may crash during seobjHasProperty(): dynamic get callback crash when called during seobjHasProperty() to determine if the propery exists. [details]
- "internal stack exhausted" error with multiple calls to jseCallFunction(): jseCallFunction() leaks ScriptEase stack space, leading to an overflow and the 'internal stack exhausted' error. [details]
- named-parameter object for wrapper functions trashed by GC: If garbage collection occurs while a named-parameter object is available to a wrapper function, that named-parameter object will be freed and its use may crash the system. [details]
- toString on functions concatenates some identifiers: When a function is being converted to a string, a required space may not be displayed after some variables. For example, "for(var foo in goo)" may become "for(var fooin goo)". [details]
- array.concat adds extra null item on initial element: If Array.prototype.concat is used on an initialy empty array, and extra element is added at the beginning. [details]
- jseMemberEx and jseIndexMemberEx do not search prototypes: Warning: In moving from version 4.30 to 4.40, and if you were using the jseMemberEx() or jseIndexMemberEx() functions without the jseDontSearchPrototype flag, then you will find that with version 4.40 members will not be located in the _prototype chain. [details]
- buffer.getString not stopping at the null character: Buffer.prototype.getString() is not terminating strings at the first null character, as specified in the documentation. [details]
- jseReturnVar may crash with strings, buffers, and objects: It is possible, although very unlikely, that variables of type jseTypeString, jseTypeBuffer, or jseTypeObject may be freed by the garbage collector before they are assigned to a script variable. [details]
- VT_ARRAY has been added to COMOBJ: Update: VT_ARRAY has been added to COMOBJ for getters (although not yet for putters). This allows scripts interacting with COM objects to retrieve array data. [details]
ISDK/Java 4.30d
- Some characters not read correctly when interpreting from a token buffer: When interpreting from a token buffer, some characters may be read back incorrectly. [details]
- Scripts interpreted from a token buffer may display erratic behavior: When interpreting from a token buffer, goto labels may become all messed up. [details]
- Floating point numbers not read correctly when interpreting from token buffer: When interpreting from a precompiled token buffer, floating point numbers will not be read correctly. [details]
- Floating point numbers not written correctly in jseCreateCodeTokenBuffer: When creating tokens with jseCreateCodeTokenBuffer, floating point numbers are written incorrectly. [details]
