It limits access to the functions inside. One advantage of it is that you can have one function named blahblah inside scope blue and have a function with the same name inside another scope.
I see now ... So all the functions inside are private . What about the other arguments I see used sometimes with scope ? Do they determine if a triggerinit function inside the scope is automatically executed ?
And does it influence the access to variables too ?
1. No, not all the function inside a scope are automatically private, you need to put the prefix "private" infront of the function to make it private... Scope just enables the ability to do this
OK thanks for the help ... I was thinking it is like the C++ classes but some sort of uberclass that makes stuff private inside unlsee otherwise stated . :thup:
I'm on a page about incorrect corrections, and spent the better part of like two hours trying to get someone to understand that -5^2 = -25, not 25, and then that post had comments get reposted because that group is self sustaining, and that person was in turn trying to explain what I just explained to them. And I'm taking that as a victory
I will be AFK for a couple of days you guys hold down the fort while I am gone. I will be checking in on my phone but that will severly limit me. Be back saturday!