public T valueForKey(Key<T> key) {
return valueForKey(key.key);
}
Well sure, if you totally change the API for valueForKey, but you're
cheating on the original question ;) You would want a <T> in there,
too, for the per-method generic.
NSArray<MyEO> = ec.objectsWithFetchSpecification(spec, MyEO.class)
I think generic EOFS would be better ... Passing in Class objects to
fulfill generics always feels a bit like hackery. It's really cheating
-- you're basically casting without using cast syntax, because you
can't enforce that the class you put in is actually related to the
objects of the fetch spec in any way, so it's as unsafe as an
arbitrary cast.
public <T> NSArray<T>
objectsWithFetchSpecification(EOFetchSpecification<T> fetchSpec) { ... }
then
EOFetchSpecification<Person> fetchSpec = ...;
NSArray<Person> people = ec.objectsWithFetchSpecification(fetchSpec);
ms
_______________________________________________
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]
