Time for a new thread! I've managed to shave another 2 seconds off of the simple benchmark for array in, down to 3.76 seconds. I have any idea on how to shave this down further, but this would require adding a fairly specialized API to the new APIs that *might* be more generally useful, but really exists for the purposes of making arrayIn work faster. I just added an ArrayAppend() API to the definitions to allow append operations to be done directly from native code. The more specialized API would be ArrayAppendString(), where the arguments would be a CSTRING pointer and a length. This will allow the appending to be done with less overhead because there will be fewer crossings of the internal/external code boundary. What do you think, should I do this? Should I prototype this first to see what the gain is?
Rick ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
