Changes between Initial Version and Version 1 of Ticket #65354, comment 16


Ignore:
Timestamp:
Jun 20, 2022, 2:46:57 PM (2 years ago)
Author:
kencu (Ken)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #65354, comment 16

    initial v1  
    2121If you try to use a feature that doesn't exist on your deployment target, the compiler will even tell you that you need to add an @availability guard for it -- isn't that helpful? Great!
    2222
    23 NOW -- we take MacPorts. We don't want to exactly follow Apple's plans here. We want to compile this code against an older SDK, say 10.15, but that older SDK doesn't know anything about the newer features in the 12.3 SDK.
     23NOW -- we take MacPorts. We don't want to exactly follow Apple's plans here. We want to compile this code against an older SDK, say 10.15, but that older SDK doesn't know anything about the newer features in the 12.x SDK.
    2424
    2525So when you try to compile code that stumbles across the newer features, even if they are guarded by an @availability block, the code will not compile. This is what you stumbled across with {{{safeAreaInsets}}}.