A reason that’s both technical and historical is that text protocols are almost always preferred in the Unix world. Well, this is not really a reason but a pattern. The rationale behind this is that text protocols allows you to see what’s going on on the network by just dumping everything that goes through. You … Read more
It could be that the cell is not visible at this moment. tableView:indexPathForCell returns nil in this situation. I solved this using indexPathForRowAtPoint this method works even if the cell is not visible. The code: UITableViewCell *cell = textField.superview.superview; NSIndexPath *indexPath = [self.tableView indexPathForRowAtPoint:cell.center];
Nice question. Here is my humble point of view: Is there a point to declaring a static function on a protocol? Pretty much the same as having instance methods declared in a protocol. The client using the protocol has to call the function on a type conforming to the protocol anyway right? Yes, exactly like … Read more
Despite its name, dataclasses.dataclass doesn’t expose a class interface. It just allows you to declare a custom class in a convenient way that makes it obvious that it is going to be used as a data container. So, in theory, there is little opportunity to write something that only works on dataclasses, because dataclasses really … Read more
Have you considered HDLC or SDLC? There’s also LAP/D (Link Access Protocol, D-Channel). Uyless Black’s “Data Link Protocols” is always nearby on my bookshelf – you might find some useful material in there too (even peruse the TOC & research the different protocols)
I wouldn’t say that something uses a wire-level protocol or doesn’t – I’d talk about which wire-level protocol it uses. Basically, if something’s communicating with a remote machine (even conceptually) then there’s some data going across the network connection (the wire). The description of that data is the “wire-level protocol”. Even within that, you would … Read more
It seems there are two use-cases of why you may want to do what you are doing. In the first use-case, Swift will allow you to do what you want, but not very cleanly in the second use-case. I’m guessing you fall into the second category, but I’ll go through both. Extending the functionality of … Read more
You Just Can’t Beat the Binary Binary protocols will always be more space efficient than text protocols. Even as internet speeds drastically increase, so does the amount and complexity of information we wish to convey. The text protocols you reference are outstanding in terms of standardization, flexibility and ease of use. However, there will always … Read more
You could use a protocol composition: extension Moveable where Self: protocol<Animal, Aged> { // … } Or just add the conformances one after the other: extension Moveable where Self: Animal, Self: Aged { // … }
NSString *className; //assume this exists Class class = NSClassFromString(className); if ([class conformsToProtocol:@protocol(SomeProtocol)]) { id instance = [[class alloc] init]; [instance create]; }