On 14/01/2008, at 2:13 PM, Mr. Pierre Frisch wrote:
I am still worried about breaking code.
Sure. Good concern.
I was more looking along the lines of adding a method like:
public NSArray<EOEnterpriseObject>
_enterpriseObjectsWithFetchSpecification(EOFetchSpecification
fetchSpecification, EOEditingContext context)
This method raises an exception at run time if the fetch
specification is raw.
I am not sure if this should be a public method it adds to the API
and is not absolutely required.
The problem here is that <EOEnterpriseObject> doesn't take it's type
from anything and so can't be cast to some subtype without
suppressing warnings. So what purpose would it serve?
It seems to me that EOFetchSpecification needs to be genericised or
this whole thing won't be pretty.
Any comments?
So, to ensure backwards api compatibility how's about this?
@deprecated
public NSArray objectsWithFetchSpecification(EOFetchSpecification
fetchSpec) {...}
public NSArray<T> enterpriseObjectsWithFetchSpecification
(EOFetchSpecification<T> fetchSpec) {...}
public NSArray<NSDictionary<String, ?>>
rawObjectsWithFetchSpecification(EOFetchSpecification fetchSpec) {....}
with regards,
--
Lachlan Deck
_______________________________________________
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]
