On Thu, Oct 13, 2016 at 5:27 PM, Ted F.A. van Gaalen via swift-evolution <[email protected]> wrote: > Please do NOT drop the current distinction between *private* and > *fileprivate* > as it is now in Swift 3 > It is needed for correct OOP.
Sorry, but that is laughable. So far I haven't seen a sole on here that seems to really know anything about OOP. You all are just copying and extrapolating on ObjC/C++/Java. Which got it all sorts of wrong from the get go. Go learn you some SmallTalk for the greater good. _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
