Re: Naming convention to identify functions with side effects

["(see below)" <yaldnif.w@blueyonder.co.uk>]

On 04/10/2008 13:30, in article
d49286ef-faa1-4b1b-8e23-0ed80c015dd2@p10g2000prf.googlegroups.com, "Marco"
<prenom_nomus@yahoo.com> wrote:

> On Oct 3, 5:28 am, "Dmitry A. Kazakov" <mail...@dmitry-kazakov.de>
> wrote:
>> Side-effects are bad in any subprograms, be them functions or procedures.
> 
>   Technically "side-effects" are being used whenever you change an
> internal state in a module, which is not always undesired.

These are not "side-effects", they are just effects.
The whole point of using computers is to cause changes of state.

> proper expression is "unrelated side-effects are bad" which violates
> the Principle of Least Surprise.

Quite so.
-- 
Bill Findlay
<surname><forename> chez blueyonder.co.uk