Finding the instance reference of an object

Dale Roberts gooberts at gmail.com
Fri Oct 31 15:03:52 CET 2008


On Oct 31, 3:15 am, greg <g... at cosc.canterbury.ac.nz> wrote:
> Dale Roberts wrote:
> > Just as the Pass By Reference idiom deserves a unique name to
> > distinguish it from Pass By Value (even though it is often Pass By
> > (address) Value internally), so Pass By Object Reference deserves a
> > unique name (even though it too is Pass By (reference) Value
> > internally).
>
> Since Python only has one parameter passing mechanism,
> there's no need to give it a name at all. If you're
> having to explain it, just explain it, and don't
> bother naming it!
>
> --
> Greg

On Oct 31, 3:15 am, greg <g... at cosc.canterbury.ac.nz> wrote:
> Dale Roberts wrote:
> > Just as the Pass By Reference idiom deserves a unique name to
> > distinguish it from Pass By Value (even though it is often Pass By
> > (address) Value internally), so Pass By Object Reference deserves a
> > unique name (even though it too is Pass By (reference) Value
> > internally).
>
> Since Python only has one parameter passing mechanism,
> there's no need to give it a name at all. If you're
> having to explain it, just explain it, and don't
> bother naming it!
>
> --
> Greg

But then why bother having any other names at all for other languages
that have only one calling mechanism, like Call By Name, Call By Macro
Expansion, etc.

If it is a different process, it needs a different name. OR, as you
suggest, no name at all, just an explanation.

But please don't give it the WRONG name!



More information about the Python-list mailing list