&arg# variables
DinkC Ref. says that &arg# is 'The first (or 2nd, etc) argument passed to a procedure'. So in this case for example:
//script a
external("script_b", "blah", 54);
//script b, procedure blah
//&arg1 == 54
Will &arg1 be 54 for the rest of that procedure or is it possible that it might change? What I mean is, is it safer to do something like int &temp = &arg1; or is that unnecessary?
//script a
external("script_b", "blah", 54);
//script b, procedure blah
//&arg1 == 54
Will &arg1 be 54 for the rest of that procedure or is it possible that it might change? What I mean is, is it safer to do something like int &temp = &arg1; or is that unnecessary?
I haven't had to deal with &arg stuff since I fixed the slot machine in Initiation... I *think* &arg1 will stay as it is until you use another "external" line. At least, that's how it should work.
It will stay the same. I had a look at the source and every script has its own arg1..9 variables.
In DinkC, they are 'pseudovariables'.. eg arg1 can be 1 in one script and 2 in another concurrently (though you may want to test this directly just to be sure)
In DinkC, they are 'pseudovariables'.. eg arg1 can be 1 in one script and 2 in another concurrently (though you may want to test this directly just to be sure)
