> Am 19.06.2012 um 23:30 schrieb Robin Lauryssen-Mitchell: >> >> Is that a 'No' to both questions? Is there another way to get the >> memory address of an object? > > Well, why do you need it? > If there is a good case, we can certainly find a solution.
In case anyone is interested...I was using both functions to pass data to external C libraries. * I would pass the object address to C, and C would return it in a callback. In the Realbasic callback function if you declare the parameter that receives the address as the correct object type, instead of as integer, then you get your Realbasic object. A work around would be to fill a Dictionary with objects and incrementing integer keys, use the key in the callback, and do a Dictionary lookup to get your object. * I would pass the string address to the library which would use...but not resize...the string. I did it this way to avoid the memory duplication inherent in String -> MemoryBlock. I don't know of a work around for that, though the RAM and performance penalty is far less today. Daniel L. Taylor Taylor Design Computer Consulting & Software Development [email protected] www.taylor-design.com _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list [email protected] https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
