Graham, I am picturing a radix trie with n-bit keys where n is 32 or 64—whichever suits your z-orders. Keys represent the z order. Each object is a leaf in the trie. In each object, store its

Are the zObjects integers? If so would it help to make them floats? Intial value 3.0; Back one 2.9 or 2.09; Forward one 3.1 or 3.01? Or have I not understood your architecture or the memory

Hi all, I Have an interesting little problem, thought I’d throw it out there and see if it stirs up any discussion…. Graphics app, wherein the user can draw stuff - arbitrary vectors on a canvas.

I learned a lot from this thread - thanks!

Jeff, Switch languages!!! Noooo…

Jeff, Couldn’t agree more…There is no need to optimize for performance here… higher level Obj-c interfaces are preferable. Yes, lots of efficiencies can be made. Unfortunately, it’s just not

On review, one thing. Don't do this:if ( [self respondsToSelector:sel] == NO ) It's a boolean method, never use an equality check for "true" or "false" on a boolean method, even if it seems to work,

This capability of Objective-C, to create classes on the fly, is one of the primo reasons why I can't understand people's fascination with Swift. Even C# can do this sort of thing, but people these

Jeff, Works great! See my implementation below… The one thing I wasn’t sure about was the types array argument for class_addMethod() The fourth param… I used ‘i’ to specify the return type

Jeff, So what you’re suggesting is… 1. Define a template implementation 2. Associate each selector pattern with that implementation That seems like it should work. I’ll give it a try and let

In the designated initialise of your Parser class, you can use class_addMethod to add whatever you like to your instance's

Jeff, Thanks for the idea… it might be a good choice… as for additional details. The caller can be seen as a controller. It dynamically allocates model (parser) classes based on context. The

You really haven't provided enough information about the caller, and you've skipped over the C programmers favourite answer.Presumably you actually NEED all those seperate selectors and can't just

Gary, interesting… I’ll have to see if Returning an NSValue wrapped scalar translates to the scalar result on the other side when I call -getReturnValue: Thanks! Sandor

Alex, I am proposing letting the runtime handle the fact the object does not respond to the selector. So, under this assumption I am inside one of two methods: -doesNotRespondToSelector: or

You might want to consider using valueForUndefinedKey: and parse it to know which value you care about, and then return the value through NSValue, which can encapsulate any value, although a

Well, I’m guessing here, but can’t you construct the method and use a perform selector, get the result and return it? It seems like you are making methods, performing them, then need to perform

Alex, Thanks for the idea. I not sure how that helps me get the return value back to the original caller. Am I missing your point? Here’s more details, in pseudo code // Controller class SEL

Would it be possible to put them in an array or dictionary as NSStrings and use performSelector on one of them if it is present within the array or dict?

I have a certain group of selectors that all follow a strict naming convention, -(Status)parseXYZ -(Status)parseRST All have one line that does the same thing and return a scalar (enum) as a