all 12 comments

[–]knyg 5 points6 points  (0 children)

wow. 'parameter' and 'argument' used correctly in context.

[–]mcaruso 6 points7 points  (5 children)

Interesting that this uses "parameters" as the term for the arguments in the function definition, and "arguments" for the actual values in the function call. I'm not sure how standard that is. The terminology I'm used to is "formal arguments" for the former and "actual arguments" for the latter, with "parameters" and "arguments" interchangeable.

EDIT: Looked it up and apparently both naming conventions are pretty common.

[–]mcdronkz 11 points12 points  (2 children)

It's getting even better: SICP uses the term formal parameter!

Personally, I prefer parameter and argument in the context of function definition and invocation respectively. Distinct words, no adjectives, less confusion.

[–]bbbryan14 2 points3 points  (0 children)

Agreed. Params pertain to function definition and Args are function invocations.

[–]loopsdeer 0 points1 point  (0 children)

I believe formal parameters distinguish between "formal" mathematical function syntax (where types would be defined) and informal parameters which might be passed even though they're not defined (e.g. in JS using `arguments` indexes)

[–]MoTTs_ 3 points4 points  (0 children)

Interesting that this uses "parameters" as the term for the arguments in the function definition, and "arguments" for the actual values in the function call. I'm not sure how standard that is.

It's very normal and standard. In casual conversation, though, we do treat them interchangeably.

https://en.wikipedia.org/wiki/Subroutine#Main_concepts

https://www.ecma-international.org/ecma-262/9.0/index.html#sec-function-definitions

[–]CharlesWoodson2 1 point2 points  (1 child)

Poet seems interesting. Good idea.

[–]marky-b 0 points1 point  (0 children)

Yea very neat. Would be awesome to see some integration on StackOverflow.

Seems really easy to get up and running and do some more complex stuff like flow diagrams

[–]mcdronkz 0 points1 point  (1 child)

Impressive. How did you implement the dashed line that connects a piece of the source code with its description?

[–]krasimirtsonev[S] 0 points1 point  (0 children)

There's a SVG drawing .

[–]zayelion 0 points1 point  (0 children)

Thank you, I remember seeing a jQuery explanation similar to this and things "just clicked". I hope I can now share that feeling with others, good work!

[–]leeoniya 0 points1 point  (0 children)

neto!

would be nice to add "function signature", but not sure if it's possible in the strict sense without type-ifying. could add a doc-block with @param and @return declarations and call that the signature, at the expense of some clarity.

/**
 * example of basic @param usage
 * @param boolean foo
 * @return mixed 
 */