1 It does not return a value to the calling code.

2 The calling code supplies the arguments when it calls the procedure.

3 This means that the calling code does not have to pass a value for it.

4 Causes the calling code to block for the specified time or until the associated process enters an idle state, whichever completes first.

5 In some cases the calling code might want to protect against such a change.

6 A generic procedure allows the calling code to pass different data types each time it calls the procedure, so it can tailor the data types to the requirements of each individual call.

7 This permits the procedure to change the value underlying the argument in the calling code.

8 Software libraries that enforce this independence between implementing and calling code are considered loosely-coupled.

9 The procedure code does not have any access to the underlying element in the calling code.

10 It eliminates any overload with an access level that prevents the calling code from calling it.

11 Specifies that an argument is passed in such a way that the called procedure or property cannot change the value of a variable underlying the argument in the calling code.

12 A demand causes the runtime to perform a security check to enforce restrictions on calling code.

13 This sort of abstraction is more useful in Java or other strongly-typed languages, because the calling code really does have a dependency on the cache object's type at compile time.