passing by refference

[Tim Peters]

[Fredrik Lundh, quotes the CLU reference manual, which has an excellent
 description of call-by-object/call-by-sharing, in particular being
 careful to distinguish it from call-by-value and call-by-reference
]

> ...
> So what's your excuse for being stuck in the early seventies? ;-)

"call by value" is very often used in the Scheme world to mean "applicative
order evaluation" aka "eager evaluation", which the Scheme standard mandates
(as opposed to lazy evaulation schemes, such as Haskell's call-by-need).
The Scheme standard itself didn't introduce this abuse of terminology, but
it's catchy if it's a distinction you need to make often; in the functional
language world, it is a distinction that needs to be made often.  So it
goes -- believe it or not, sometimes different people mean different things
by the same words <wink>.  The business of warping "call by value" to mean
"the internal address of the object is the value" doesn't seem common even
in the functional world, though.