Got some details to deal with first.
MontCode has seriously only been live for 21 days now so a lot of the details are still being worked up.
I’ve been blessed.
(I'll not be at the meeting, Jonathan, but maybe I can help afterwards)
shift/unshift are front
I only know @rmaylie9560 because I spent far to much time trying to understand the stupidness that is the names to shift/unshift.
yea I mean i get that stuff but some of the orders of it and where the variables are called are confusing me mix that in with tiredness and the fact that suddenly they have all this JSON stuff at the bottom where JSON has not been mentioned once and i'm completely clueless. Think I'm gonna sleep though I'll deal tomorrow
Here is the entire code for reference
function nextInLine(arr, item) {
// Your code here
arr.push(item);
removed = arr.shift();
return removed; // Change this line
}
// Test Setup
var testArr = [];
// Display Code
console.log("Before: " + JSON.stringify(testArr));
console.log(nextInLine(testArr, 1)); // Modify this line to test
console.log("After: " + JSON.stringify(testArr));
So on the Stand In Line problem, at the bottom you can see the call
nextInLine(testArr, 1)
And at the top you see a very similar line function
nextInLine(arr, item) {
Even tho those lines are similar (both have nextInLine with two things in parenthesis, the first one in the function definition because it has the function keyword at the start.
That makes the second one the function call.
In the function definition, the things inside the () are called parameters. In the call, they are called arguments.
After the function declaration, testArr was defined (as an empty array).
That next to last line calls nextInLine and sends two arguments (kinda like a bash command).
So arr gets automatically defined as the first argumentand item is defined at the second argument. In the above code it's the same as if it said
var arr = testArr; //The first argument and the first parameter.
var item = 1;//The second argument and the first parameter.