News for hackers. Stuff that matters.
Re:The beauty of bitwise AND by dingo_bat on Wednesday August 03, 2016 @11:16PM (#12223153)
I always thought ^ is the XOR operator, not AND.
Re:The beauty of bitwise AND by posterboy on Wednesday August 03, 2016 @11:42PM (#12223234)
In boolean algebra, * (a dot, actually) and + are used for And and Or and the usual rules about association and commutation are used (PEMDAS, kinda, ommiting the * on occasion). Sometimes, what I might call, up arrow and down arrow are used, looking similar to ^ and v, in relation to set arithmetic symbols for the union and intersection oprators.
Re:The beauty of bitwise AND by svalorzen on Thursday August 04, 2016 @03:55AM (#12224097)
Another way to easily remember the arrows is to associate them with words: ^ with the A of and, and v with the V for vel (Latin for or). I always did this in logic class since I would always get confused otherwise.
Re:The beauty of bitwise AND by TeMPOraL on Thursday August 04, 2016 @08:46AM (#12225113)
I remembered these and union/intersection sign by imagining balls falling on the symbols from above - in case of V (OR) they would end up inside the symbol, which suggest summing/union, and in case of ^ (AND) they would get split and collect on opposite sides.
Re:The beauty of bitwise AND by dnautics on Thursday August 04, 2016 @06:38AM (#12224629)
Also useful is making the arrows round-ended makes the the union/intersection signs, with or being union and and bring intersection (as it would be with the corresponding indicator functions).
Re:The beauty of bitwise AND by Tomte on Thursday August 04, 2016 @12:32AM (#12223408)
Yes, it is.

But ^ and ∧ are different.

Re:The beauty of bitwise AND by turbohedgehog on Thursday August 04, 2016 @12:41AM (#12223429)
⊕ would be XOR using mathematical notation
Re:The beauty of bitwise AND by kkaja on Wednesday August 03, 2016 @11:43PM (#12223236)
The post is using boolean algebra symbols.
Re:The beauty of bitwise AND by coinomega on Thursday August 04, 2016 @12:55PM (#12226879)
I used the notations found in FIPS 180-4 http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf