05-28-2025, 10:18 PM
@developers of compiler of QB64pe...
I found confounding the example of PhilofPert at #40 about variable a.
It is a single variable declared at beginning of the code as DIM SHARED so global and visible anywhere...
then it has been passed as parameter to sub ADDRANDOM (a) and this last has in declaration a parameter of kind single with the same name a.
In the Sub AddRandom (a) the variable has been used as counter in a FOR/NEXT loop. So it has been changed taking the values before 1 and then 2 and ending in exiting the FOR loop as value 3.
The parameter a has not been changed because it has been passed for value to the sub.
But why the compiler does not change a because it is the global anywhere visible SHARED variable? Is there no conflict using a SHARED variable as parameter passed for value to a procedure? it is already visible in the procedure! Does the compiler always overwrite the condition of SHARED variables if they have been passed as parameters with limitation of the access to their value?
In other words, if we could observe 'a' from inside SUB AddRandom and from main at the first cycle of FOR it should be equal to 1 in both sides, while ending the procedure SUB the compiler restore the entering in sub value of 'a' .
Is it the same in QBasic?
I found confounding the example of PhilofPert at #40 about variable a.
It is a single variable declared at beginning of the code as DIM SHARED so global and visible anywhere...
then it has been passed as parameter to sub ADDRANDOM (a) and this last has in declaration a parameter of kind single with the same name a.
In the Sub AddRandom (a) the variable has been used as counter in a FOR/NEXT loop. So it has been changed taking the values before 1 and then 2 and ending in exiting the FOR loop as value 3.
The parameter a has not been changed because it has been passed for value to the sub.
But why the compiler does not change a because it is the global anywhere visible SHARED variable? Is there no conflict using a SHARED variable as parameter passed for value to a procedure? it is already visible in the procedure! Does the compiler always overwrite the condition of SHARED variables if they have been passed as parameters with limitation of the access to their value?
In other words, if we could observe 'a' from inside SUB AddRandom and from main at the first cycle of FOR it should be equal to 1 in both sides, while ending the procedure SUB the compiler restore the entering in sub value of 'a' .
Is it the same in QBasic?