[v2] DllCall * or P (suffix) type description

[iPhilip]

I would like to recommend that the following sentence be added at the end of the first paragraph in the * or P (suffix) type description:

The output value (if any) of numeric parameters with the * or P suffix is ignored if the script passes a plain variable containing a number. To receive the output value, pass a VarRef such as &myVar or an object with a Ptr property.

Thus, the paragraph would read as follows:

Append an asterisk (with optional preceding space) to any of the above types to cause the address of the argument to be passed rather than the value itself (the called function must be designed to accept it). Since the value of such an argument might be modified by the function, whenever a VarRef is passed as the argument, the variable's contents will be updated after the function returns. For example, the following call would pass the contents of MyVar to MyFunction by address, but would also update MyVar to reflect any changes made to it by MyFunction: DllCall("MyDll\MyFunction", "Int*", &MyVar). The output value (if any) of numeric parameters with the * or P suffix is ignored if the script passes a plain variable containing a number. To receive the output value, pass a VarRef such as &myVar or an object with a Ptr property.

[lexikos]

That's redundant, but I see that "whenever a VarRef is passed as the argument" maybe isn't explicit enough for some.

However, I think we can drop "of numeric parameters with the * or P suffix". Repeating the redundant "parameters with the * or P suffix" seems unnecessary, and IIRC this applies just the same to "Str*" (with the "output value" in that case typically being a new string pointer, not pointing to the original variable's string buffer).