|is state bad? firstname.lastname@example.org (1994-12-24)|
|Re: is state bad? email@example.com.OZ.AU (1995-01-05)|
|From:||firstname.lastname@example.org (Amy Caplan)|
|Keywords:||design, OOP, question|
|Organization:||The Whole Earth 'Lectronic Link, Sausalito, CA|
|Date:||Sat, 24 Dec 1994 02:02:34 GMT|
I think I have encountered a viewpoint that local state is bad,
presumably because it makes programs more difficult to understand
and debug. (e.g. violating the notion of "referential transparency").
This would seem to be in conflict with the "object oriented" trend,
which often encourages local state.
1. Is this my imagination, or is this really a widely shared viewpoint?
2. If so, are there any objective measures that show that
a routine with local state is more 'complex' for human or compiler
than an equivalent routine that operates without local state,
or at least a good argument to this effect?
Thanks for any enlightenment.
Return to the
Search the comp.compilers archives again.