←back to thread

156 points todsacerdoti | 3 comments | | HN request time: 3.411s | source
Show context
userbinator ◴[] No.44506358[source]
Somewhat less frequently, I also hear "invoke" or "execute", which is more verbose but also more generic.

Incidentally, I find strange misuses of "call" ("calling a command", "calling a button") one of the more grating phrases used by ESL CS students.

replies(7): >>44506396 #>>44506421 #>>44506500 #>>44506580 #>>44510160 #>>44510878 #>>44511635 #
pansa2 ◴[] No.44506396[source]
> strange misuses of "call"

My favourite (least favourite?) is using “call” with “return”. On more than one occasion I’ve heard:

“When we call the return keyword, the function ends.”

replies(3): >>44506779 #>>44506910 #>>44506977 #
jamesfinlayson ◴[] No.44506779[source]
I remember someone in university talking about the if function (which ostensibly takes one boolean argument).
replies(5): >>44506886 #>>44506915 #>>44507329 #>>44508128 #>>44509940 #
1. Findecanor ◴[] No.44506886[source]
There are languages in which `if` is a function.

In in Tcl, `if` is called a "command".

replies(1): >>44509377 #
2. spacechild1 ◴[] No.44509377[source]
Also in Smalltalk and sclang (Supercollider language)
replies(1): >>44510065 #
3. kitd ◴[] No.44510065[source]
Or anything Lispy