Dear all, I’ve migrated to java 8 in development and deployment and am now dabbling with new “features”.
Optionals seem a potentially good way of documenting nullability although the syntax is currently rather cumbersome it seems likely that in future versions, the syntax will improve. However, key value coding fails when an object is encapsulated by an Optional. Intuitively, these should be unwrapped during KVC so that “normal” behaviour continues - i.e. as KVC gracefully handles null pointers in arbitrary key paths it should gracefully handle optionals containing either a value or null. How would the handling of KVC be patched for future java versions? Is this something fixable now? Does all KVC work via NSKeyValueCoding.DefaultImplementation or are there multiple implementations? I used to have a java decompiler working but haven’t set this up since upgrading eclipse so it has been difficult to fathom the internals. Mark -- Dr. Mark Wardle Consultant Neurologist, University Hospital Wales, Cardiff, UK Deputy Sub-Dean for Assessments and Honorary Lecturer, Cardiff University Email: mark.war...@wales.nhs.uk or m...@wardle.org Twitter: @mwardle Telephone: 02920745274 (secretary) or facsimile: 02920744166
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
