Re: [Pyobjc-dev] Initial memory usage
Brought to you by:
ronaldoussoren
From: Bill B. <bb...@ma...> - 2009-10-01 21:34:49
|
On Oct 1, 2009, at 2:26 PM, Samantha Atkins wrote: > I am curious about this. These tables in Objective C runtime don't take a lot of space. What sort of overhead is introduced converting the information to pyobjc equivalents? On the face of it I don't see why this would take a lot of memory or be all that computationally expensive. Isn't this information needed not just for dir() but for sending any message to an objc object? So why not pay the scan cost once at class/bundle load time and then forget about it? Assuming it can be made reasonably efficient of course. I guess I should finally get around to looking in the guts of this bridge. It is somewhere on my bloated todo list. It isn't the ObjC metadata directly, but a combination of that and the bridge support XML files; all that XML is dragged in, shoved into data structures and kept around. b.bum |