On Sun, Aug 30, 2015 at 8:20 PM, Richard A. O'Keefe
The print statement has an EFFECT. That effect is not a *SIDE* effect. Here's the definition of "side effect":
1. A subsidiary consequence of an action, occurrence, or state of affairs; an unintended secondary result. 2. An effect (usually for the worse) of a drug or other chemical other than that for which it is administered
In the case of the little program above, the fact that output is sent to a destination is neither subsidiary, nor unintended, nor secondary, nor other than that for which the program was constructed.
I flatly deny that "UNINTENDED ... results" are what attracts ANYONE to programming. Effects, *YES*; *side* effects, NO.
Wrong definition, my friend. https://en.wikipedia.org/wiki/Side_effect_(computer_science)