Since the same identifier name can't be reused / its a local variable being called outside of its scope shouldn't this cause an error?

ANONYMOUS wrote:

Since the same identifier name can't be reused / its a local variable being called outside of its scope shouldn't this cause an error?

Why can't the same identifier name be reused? After the function ends the program would believe it is seeing the identifier for the first time and so would initialize it to 0.

This assumption was based off 'you cannot introduce a new function if its name is already used as a variable's name, or introduce a new variable if its name is already used as a function's name.' from https://secure.csse.uwa.edu.au/run/help2002?p=np&opt=U151 and 'a function's parameters and any other identifiers used in a function body are local to that function, and become unavailable when the function's execution completes'.

I must've misunderstood the meaning of 'becomes unavailable', is the correct rules that only function identifiers must be wholly unique, variables can be reassigned within their scope, and any local identifiers (function parameters + identifiers used in a function body) can be assigned/used as 'new' variables outside of their scope?

Thank you for all of the help!

https://secure.csse.uwa.edu.au/run/help2002?p=np&opt=B388&year=2024 do we instead follow this and not allow any duplicate names of variable reassignment now??

ANONYMOUS wrote:

https://secure.csse.uwa.edu.au/run/help2002?p=np&opt=B388&year=2024 do we instead follow this and not allow any duplicate names of variable reassignment now??

Yes, otherwise if you have already done it Amitava said you can state the assumptions you made in a file. So, you can do either, just state what assumption you made.