LWN.net Logo

Why it's so hard to understand?

Why it's so hard to understand?

Posted May 29, 2010 0:25 UTC (Sat) by baldridgeec (guest, #55283)
In reply to: Why it's so hard to understand? by khim
Parent article: The road forward for systemd

I've had this discussion so many times and I still can't believe people are thinking like that. Guys, OR and XOR are different operations! Please open the logic textbook and read about difference between them! This is vital if you want to talk about systemd!
Either implicit dependencies are used, and you rely on socket activation, but you don't start daemons as early as they could be

I haven't done enough thought experiments or study of the init process limitations to have any kind of coherent input about systemd's particulars (despite having read Lennart's blog post with interest last week), but I do have a rather decent knowledge of linguistics in general, and English in particular.

"Either" is a word which introduces a parameter to the conditional expressed by "or." It is a flag which notifies the reader that the first and second clauses of the conditional are mutually exclusive.

In other words:

("OR" != "XOR") == 1
but also
("XOR" == "Either..or") == 1


(Log in to post comments)

Why it's so hard to understand?

Posted Jun 4, 2010 23:37 UTC (Fri) by Wol (guest, #4433) [Link]

"Either" (in normal English usage) does *not* imply the two sides of the "or" are exclusive.

"You can borrow my car if you do either A or B" - in other words I don't care which you do and you could do both if you wish. "either" is a filler word which implies "xor" but doesn't require it. If you *really* mean XOR, you have to say "either but not both".

Cheers,
Wol

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds