15 ms·
I think there is value in actually having a term for Java's (and Python's, and Ruby's, and Javascript's) argument-passing semantics, what was called "call by sh
by masklinn 9y ago
I think there is value in actually having a term for Java's (and Python's, and Ruby's, and Javascript's) argument-passing semantics, what was called "call by sharing" in CLU (and sometimes called pass-reference-by-value in some communities), because it's sufficiently different than either pass-by-reference or "full-fledged" pass-by-value that using these terms gets confusing, especially to people not learning them… which would be those you're using these with as the others have no issue understanding them.
I do also think lisper is absolutely terrible at making that point.
- Izkata 9y agoI like call-by-sharing. Every single one of these arguments between call-by-value and call-by-reference I've seen always fall apart because the arguers never accept that there's (at least) 3 forms of calling, whatever we want to call them. > and sometimes called pass-reference-by-value in some communities Or call-by-value-of-reference. It's too much of a mouthful, but is the usual alternative I hear.