4 ms·
If you're a student in mattmight's class, you shouldn't read this. N hfrshy gbby gung negvpyr zvffrf vf gung frg qvssrerapr pna or vzcyrzragrq (zhpu zber rssvp
by jemfinch 15y ago
If you're a student in mattmight's class, you shouldn't read this.
N hfrshy gbby gung negvpyr zvffrf vf gung frg qvssrerapr pna or vzcyrzragrq (zhpu zber rssvpvragyl guna uvf dhnqengvp nytbevguz), hfvat naq .
Vs lbh unir gjb svyrf N naq O juvpu ner frgf (v.r., ab vagreany qhcyvpngrf), N - O pna or rkcerffrq ol "fbeg N O O | havd -h".
Bs pbhefr, vs lbh TAH pberhgvyf ba lbhe flfgrz (naq vs lbh'er ehaavat Yvahk, lbh nyzbfg pregnvayl qb), vg'f rira rnfvre naq zber rssvpvrag: "pbzz -23 N O".
- mattmight 15y agoThat's the exercise at the bottom of the page. ;) I hope my students don't see this comment. Edit: Thanks for "encrypting" your post. Decrypting it in one tweet's worth of sed will be next Tuesday's homework.
- joshcorbin 15y agoReally? Sed? Me thinks they should TRy harder ;-)
- antics 15y agoMatt, you should know better. You've scared everyone who doesn't read HN out of the class.
- telemachos 15y ago>> Of course, if you GNU coreutils on your system (and if you're running Linux, you almost certainly do), it's even easier and more efficient: "comm -23 A B". Maybe I'm misunderstanding your point, but I don't think GNU's coreutils is the only way to get comm[1]. Nice update to the original post, by the way. :) [1] http://pubs.opengroup.org/onlinepubs/9699919799/utilities/comm.html http://pubs.opengroup.org/onlinepubs/9699919799/utilities/co...
- jemfinch 15y agoNo, you understood my comment; I assumed since the manpage I was looking at made no reference to a standard, that it was nonstandard. It seems you're right, and comm(1) is more widely available, excellent.