Post B6Cp0qc0rtw9wEPhoW by tomjennings@tldr.nettime.org
 (DIR) More posts by tomjennings@tldr.nettime.org
 (DIR) Post #B6Coch4agOi9P4GNNo by tomjennings@tldr.nettime.org
       1 likes, 0 repeats
       
       Abomination, I tell you./* Receive one or more files using ZMODEM. */far zrecv(fn,nl,ll)char *fn;/* path to receive to */char *nl;/* created list of received files */unsigned ll;/* its maximum size */{int error;...
       
 (DIR) Post #B6CohgDpH4hWDBxcB6 by lanodan@queer.hacktivis.me
       0 likes, 0 repeats
       
       @tomjennings So like you wait for a null byte twice and then you have the size?
       
 (DIR) Post #B6Cp0qc0rtw9wEPhoW by tomjennings@tldr.nettime.org
       1 likes, 0 repeats
       
       @lanodan That's a pre-ANSI function declaration. fn, nl and ll are declared type char *. That's normal enoughIt's the far that abominable. x86 SEGMENTATION.
       
 (DIR) Post #B6CpHUKexRFhlGEQ2i by lanodan@queer.hacktivis.me
       0 likes, 0 repeats
       
       @tomjennings Aah somehow I didn't notice the far.And yeah K&R C, I thought it was one of those things where a protocol is described via C headers (I've seen that quite few times).
       
 (DIR) Post #B6CyXysu22EgjqBhR2 by tomjennings@tldr.nettime.org
       1 likes, 0 repeats
       
       @lanodan ZMODEM was a neato file transfer protocol, usage peaked in the bbs days on the fidonet. It could do windowed streaming like tcp, its proto overhead could be crazy low with 1024 byte packet size. It adjusted packet size based on error rate. Chuck was a smart guy. Im thinking of adapting it for a mp/m machine to Linux box "file server"https://en.wikipedia.org/wiki/ZMODEM?wprov=sfla1 not sure if it will fit in z80. 32 bit ints are very cumbersome (quad precision).