Re: Iterating over an array style question

Tom Anderson <twic@urchin.earth.li> writes:


  Hey, don't steal my opinions! This is already my opinion!?

  Well, after all, statements in imperative languages
  might have ?side-effects? if we agree to use this
  term for any effects not specified in the documentation.

  For example, the execution of the following statement
  has two effects:

      ++i;

      1st It increments i.

      2nd It heats my room (via the microprocessor, which
            gets heated by the execution).

  However, ?2nd? is not a specified effect, so it might be
  called ?side-effect?. (Writing data to a memory of n bits
  at Temperature T will at least create the heat k ln(2) T,
  where k is Boltzmann's constant.)

  ?) For example, in this post, I prefer ?effect? to
  ?side-effect? in 2004:

|Message-ID: <applicatively-20041031183814@ram.dialup.fu-berlin.de>
|(...)
| To me, "imperatively" means effect[1]-based and "functionally"
|(...)
| [1] aka "side-effect", i.e., a change of state happening

  Here, I express this opinion in German in 2006:

|Message-ID: <Kriterien-20060831221618@ram.dialup.fu-berlin.de>
|(...)
|Ich bin der Meinung, da? das, was man "side-effect" nennt,
|am besten "Wirkung" genannt werden sollte

  (?It is my opinion, that, what is called "side-effect", should
  better be called "effect")