Re:The Story of the Ping Program (1997)
by krossitalk on Tuesday July 30, 2019 @12:53PM
(#20566713)
Sadly the link to the source redirects to the US Army home page now. Anyone got a link?
[ Parent
| on HN ]
Re:The Story of the Ping Program (1997)
by themattress on Tuesday July 30, 2019 @12:54PM
(#20566728)
Looks like it’s fixed. Worked for me: https://ftp.arl.army.mil/~mike/ping.html
Re:The Story of the Ping Program (1997)
by krossitalk on Tuesday July 30, 2019 @01:02PM
(#20566802)
No, the link he provided in the document to the original PING source.
It's supposed to go to http://ftp.arl.army.mil/pub/ping.shar
But ends up at https://www.arl.army.mil/www/default.cfm
Re:The Story of the Ping Program (1997)
by birdman3131 on Tuesday July 30, 2019 @01:46PM
(#20567271)
Re:The Story of the Ping Program (1997)
by birdman3131 on Tuesday July 30, 2019 @01:46PM
(#20567273)
Looks like it's viewable here: https://github.com/iputils/iputils/blob/master/ping.c
obviously not the original source code from 1983.
nope, but derived.
this is pretty close:
https://www.tuhs.org/cgi-bin/utree.pl?file=4.3BSD/usr/src/et...
pr_pack( buf, cc, from )
char *buf;
int cc;
struct sockaddr_in *from;
{
I know this ship has sailed, but after reading through the code you linked to, I finally understand the merit to this old-style C function definition syntax, and actually think it might look nicer than the modern way of doing the same thing for longer parameter lists: pr_pack( char *buf,
int cc,
struct sockaddr_in *from )
{
It reminds me of how in TypeScript, if a function gets too many arguments, I'll split them out into an interface, and use destructuring to get to each element in the actual parameter list for convenience.