News for hackers. Stuff that matters.
Re:Relational shell programming by jemfinch on Thursday January 12, 2012 @11:20AM (#3456829)
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".

Re:Relational shell programming by mattmight on Thursday January 12, 2012 @11:25AM (#3456851)
That'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.

Re:Relational shell programming by joshcorbin on Thursday January 12, 2012 @05:26PM (#3458248)
Really? Sed? Me thinks they should TRy harder ;-)
Re:Relational shell programming by antics on Thursday January 12, 2012 @05:40PM (#3458293)
Matt, you should know better. You've scared everyone who doesn't read HN out of the class.
Re:Relational shell programming by telemachos on Thursday January 12, 2012 @11:28AM (#3456872)
>> 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/co...

Re:Relational shell programming by jemfinch on Thursday January 12, 2012 @11:40AM (#3456919)
No, 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.