Talk:Side effect (computer science)
From Wikipedia, the free encyclopedia
Contents |
[edit] Naming
In the future, this article should live at side effect (computer science)...
- Yes. The medical meaning is by far the most prominent. --Tarquin
[edit] Functions without side-effects are idempotent?
I was thinking; are functions without side-effects per definition idempotent? If so; would it be worth mentioning idempotence in this article? --EdSchouten 14:14, 18 March 2006 (UTC)
- No. Idempotence means it has the same effect whether used once or multiple times. Functions without side effects should have no side effect at all. --Spoon! 04:35, 22 October 2006 (UTC)
[edit] side-effects are also I/O
I think side effects are not just state, they are also I/O. More generally, any effect besides returning a value is a side-effect. Ideogram 19:27, 28 May 2006 (UTC)
[edit] not just functions
This article should not concentrate on functions; the concept extends to the evaluation of any expression. For instance, in C, the expression "x++" is side-effecting, as is the expression "getc(stdin)". — brighterorange (talk) 17:17, 16 June 2006 (UTC)
- Wouldn't x++ be better listed as an example of a destructive update? --maru (talk) contribs 01:15, 21 June 2006 (UTC)
[edit] Explicit asignement is not a side effect
the article states that, in imperative programming, side effects make program work, however, if I'm not wrong, imperative programs can (or must) perfectly work without any side effects at all, by using just explicit asignement sentences ¿ isn't it ?
- I think so, but the article says imperative programming often uses side effects, not that it must use them to work at all. --Gwern (contribs) 23:34 22 February 2007 (GMT)
