In message <[EMAIL PROTECTED]>, Aaron "Castironpi" Brady wrote:
> On Oct 2, 12:52 am, Lawrence D'Oliveiro <[EMAIL PROTECTED] > central.gen.new_zealand> wrote: > >> In message <[EMAIL PROTECTED]>, >> Steven >> >> D'Aprano wrote: >> > On Wed, 01 Oct 2008 22:14:49 +1300, Lawrence D'Oliveiro wrote: >> >> >> In message >> >> <[EMAIL PROTECTED]>, >> >> Aaron "Castironpi" Brady wrote: >> >> >>> Do you ever want to scream from the rooftops, "'append' operates by >> >>> side-effect!"? >> >> >> No. It's an effect, not a side-effect. >> >> > "Side-effect" has the technical meaning in functional languages of any >> > change of state that isn't the creation and return of a function >> > result. >> >> "Side" means that it happens as the by-product of returning a function >> result. "<list>.append" isn't a function, it's a procedure. Hence the >> modification of the list is the primary effect, not a side effect. > > I was using the technical definition from functional languages ... Which is where the use of "side" would make sense, given that functional languages are full of functions, not procedures. -- http://mail.python.org/mailman/listinfo/python-list
