> Writing "(A . B)(x) == (B . A)(x)" or "A . B == B . A" would make the commutative part of the formula a bit more visible..
It definitely would have made it clearer.
> ..a general version of the commutative property, not a specialized version for function composition..
Ah, but actually the case where a binary operator is commutative over its entire domain is the special case (in the mathematical sense, blah).
It's just that in programming we don't often (explcitly) deal with non-commutative binary operators, and even less often with non-commutative operators which are commutative when restricted to a subset of their domain.
Here's a quick roughly-phrased example:
Consider a rubik's cube. Think of a "move" as a function which maps a cube configuration to another configuration. This is a non-commutative group with elements these cube-config-maps and binary operator function composition. Now, for any two moves f and g which don't "interfere" (e.g. rotate top, rotate bottom), (f . g) == (g . f).
Posted Apr 20, 2012 1:13 UTC (Fri) by mmorrow (subscriber, #83845)
[Link]
Here's a better example:
The "elements" are C stmts thought of as mappings of memory configurations, and the binary operator is `;`. This is a monoid with identity element the empty C stmt.
Define,
modify(S) := the set of memory locations statement S *may* modify.
So now, `;` is commutative for every pair of statements S,T which *must not* (i.e. cannot under any possible dynamic execution path) modify one or more of the same memory locations.
(S ; T)===(T ; S) <==> modify(S)/\modify(T)==empty_set
(where "===" := equivalence wrt effect on memory)
PHP: a fractal of bad design (fuzzy notepad)
Posted Apr 20, 2012 1:37 UTC (Fri) by mmorrow (subscriber, #83845)
[Link]
Actually that's not quite correct, it's more like:
(S ; T)===(T ; S)
<==>
modify(S)/\modify(T)==empty_set
AND
read(S)/\modify(T)==empty_set
AND
read(T)/\modify(S)==empty_set
or something along these lines, but the idea is clear.
PHP: a fractal of bad design (fuzzy notepad)
Posted Apr 20, 2012 8:19 UTC (Fri) by mpr22 (subscriber, #60784)
[Link]
Programmers tell their programs to subtract, divide, and/or shift fairly frequently.