On 30/Sep/2010, at 2:50 AM, David Avendasora wrote: > What this would mean for this situation is that we create 2 new Prototypes > DateOnly and DateWithTime and deprecate Date. The next time someone opens > their project that uses the deprecated Date prototype they'll get a warning > on their Model telling them that the Date prototype they are using has been > deprecated, and the next time they EOGenerate the getters/setters will be > deprecated as well. Any methods that use them will show as deprecated and > have the deprecationNote from the UserInfo in the mouse-over , e.g., > "mySetter uses a deprecated prototype in the model. You should use either > DateOnly or DateWithTime instead of Date as the Date prototype is horribly > broken and likely doesn't do what you think it does."
I like this approach as it allows existing projects to opt in as desired. ;-) M. _______________________________________________ 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]
