On Tue, Dec 21, 2010 at 2:07 PM, Ramsey Gurley <[email protected]> wrote:
> > On Dec 21, 2010, at 2:52 PM, John Huss wrote: > > I don't think that will work, will it? It has to call a method. > > > I think you're right. Vars look like they will eat a lot of memory on > second glance. > > One solution that would work very well would be to refactor ERXKey and > create a base class that has a much smaller API that is non-conflicting, > then the ERXKey subclasses could use that instead. > > Most of that big api is pretty useful though. > When you get to the end of a key path you can return a full ERXKey class. But the in-between ones (the generated subclasses) really only need to be able to .append. In fact you could ditch ERXKey and just use a simple string builder until you have a complete path, then turn it into an ERXKey. It would add an extra step to the call, but it could work. MovieRole.pathTo.talent().photo().photo().erxkey().eq(...) But it's only the no-args methods that conflict and some of them (the static ones) aren't really relevant for building a path. If you remove the static ones, then you just have a handful of possibly conflicting names - like key(), asc(), ascs(), desc(), descs() So I think either approach is workable.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
