This would be a pretty radical change that would break a lot of code. At the moment the raw rows is a boolean in the EOFetchSpecification, I agree that this would be a nice improvement but are we ready for it?

Pierre
--
Pierre Frisch
[EMAIL PROTECTED]


On Jan 7, 2008, at 20:03, Mike Schrag wrote:

.... pretend .... you ... never mentioned that?

I suppose your fetch spec would then be EOFetchSpecification<NSDictionary> and maybe it would just work out?

ms

On Jan 7, 2008, at 10:04 PM, Mr. Pierre Frisch wrote:

And what do you do with raw rows?

Pierre
--
Pierre Frisch
[EMAIL PROTECTED]


On Jan 7, 2008, at 7:36, Mike Schrag wrote:

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);


_______________________________________________
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/pierre%40apple.com

This email sent to [EMAIL PROTECTED]

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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]

Reply via email to