> In the low level world, there is no such thing as an invalid address; both > 0x0 and ~0x0 are perfectly valid byte pointers. So using something else than > 0x0 for Swift invalid pointer just shuffle the problem around.
Let me state it this way: You cannot write a fully-conforming C compiler for a platform which does not have some way to represent an invalid pointer. However C does it, Swift can do the same thing. -- Brent Royal-Gordon Architechies _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
