On Timer only allows SUB with Integer argument error?

[Cobalt]

Just what is this about?

Code: QB64: [Select]

1. DIM Board(50, 30) AS INTEGER
2. CONST TRUE = -1, FALSE = NOT TRUE
3.  
4. CONST MaxX = 50
5. CONST MaxY = 30
6. T1& = _FREETIMER
7. on timer(t1&,.025) AgeBoard(Board())
8.  
9. sub AgeBoard(B())
10.  FOR x%% = 1 TO MaxX
11.   FOR y%% = 1 TO MaxY
12.    B(x%%, y%%) = FALSE
13.  NEXT y%%, x%%
14. end sub
15.  

ERROR:"Only SUB arguments of integer-type are allowed on line 7:

and yet Board is an integer type

why would it matter what type is sent to the sub by the Timer?

or is there something else going on and that is just some generic error coming up and not really telling what the true error is?

[SMcNeill]

Board isn’t an integer; it’s an ARRAY of integers.

[bplus]

That is curious.

Consulting Help on ON TIMER, it says "SUB parameter values are passed by value and should be SHARED or literal values!"

Which means even if it would take an array, it would be a temp copy of it and you could not save changed values through the arguments.

Looks like you will have DIM SHARED the array so that SUB would need no arguments.

Oh wait, maybe it's not just one array you want to change... ;(

[RhoSigma]

Strings and Arrays are ALWAYS passed as reference (not BYVAL) to any SUB/FUNCTION call according to my findings. Had a similar problem a while back, and did investigate into it as far as possible. It makes sense, as Arrays and Strings arguments in fact are only the start addresses of the string/array, hence references to the actual string/array arguments. In that thinking, it won't probably work with UDTs either (exept if you pass just a single UDT element, not the entire UDT structure).

But as you can use SHARED variables as well to pass variables into a SUB/FUNCTION, I see no reason for bothering the developers, I think SUBs/FUNCTIONs are complicated enough with its internal implementation in QB64.

[SMcNeill]

Is my medication breaking my brain again, or....

****************

EDIT:  Never mind.  My poor brain is broken again.  I was thinking in terms of DECLARE LIBRARY for some reason.  I’m just gonna shut up and go back to bed.  LOL!

[Petr]

This "error" is not an error. The command ON TIMER simply does not have a specified value from the field, which have to use. I think it's more of a bad combination of commands by the programmer.

[bplus]

Strings and Arrays are ALWAYS passed as reference (not BYVAL) to any SUB/FUNCTION call according to my findings. Had a similar problem a while back, and did investigate into it as far as possible....

Which makes the case for ON TIMER that much more curious. It is NOT ALWAYS.

http://qb64.org/wiki/ON_TIMER(n)
  [ You are not allowed to view this attachment ]  

[Cobalt]

I was just hoping to make a more versatile program an not have anything shared. but ahwell.

Still wonder why a sub called by an on timer would be different than just calling the sub.

But I guess I'll just have to use SHARED. Poomp!

[Petr]

Big apology, Cobalt. I misunderstood the problem described. This is pretty stupid that the ON TIMER command is studying the parameters of the called subprocess. Why is ON TIMER interested about SUB parameters? It just has to call a subroutine.A really nonsensical restriction.

[SMcNeill]

Which makes the case for ON TIMER that much more curious. It is NOT ALWAYS.

http://qb64.org/wiki/ON_TIMER(n)
  [ You are not allowed to view this attachment ]

I think Rho has hit the nail on the head with: “Strings and Arrays are ALWAYS passed as reference (not BYVAL) to any SUB/FUNCTION”.

ON TIMER *only* accepts values being passed to it BYVAL, (as per the screen shot bplus provides points out), so it can’t accept strings or arrays as a parameter type.

[bplus]

I think Rho has hit the nail on the head with: “Strings and Arrays are ALWAYS passed as reference (not BYVAL) to any SUB/FUNCTION”.

ON TIMER *only* accepts values being passed to it BYVAL, (as per the screen shot bplus provides points out), so it can’t accept strings or arrays as a parameter type.

OH man, I missed the first few words of what Rho said, Strings and arrays, dang! I was skipping over that assuming he was saying all parameters were passed by reference which is true enough that we can pass arrays and change them in a sub and the main code accepts the change.

[RhoSigma]

And I've an idea why it should be SHARED variables or literals:

Assume you define a variable X in the your main module, which shall be used as parameter to the ON TIMER() DoSomething(X) call...

Now think about the nature of ON TIMER, you define a time interval for the function call, but who says that your program is right executing anywhere in your main module when the interval is elapsed and the DoSomething(X) function is called.

What happens, when your program is executing within any of your SUBs or FUNCTIONs when the timer is ready to call DoSomething(X)? What is passed then? Because variable X is not known in your SUBs/FUNCs unless SHARED or maybe defined as a local X within the SUB/FUNC.

Literals will work always, as it's like a constant value.

[Jack002]

I have never used ON TIMER.
The help said this
The ON TIMER statement sets up a timed event to be repeated at specified intervals throughout a program when enabled
So, is it like an interrupt?
If so, I understand the above post. You might be in a function or subroutine somewhere that does not have the scope of this parameter, then it makes sense that it can only take shared vars and literals.

What kinds of things do you use ON TIMER for?

[bplus]

I have never used ON TIMER.
The help said this
The ON TIMER statement sets up a timed event to be repeated at specified intervals throughout a program when enabled
So, is it like an interrupt?
If so, I understand the above post. You might be in a function or subroutine somewhere that does not have the scope of this parameter, then it makes sense that it can only take shared vars and literals.

What kinds of things do you use ON TIMER for?

Yes Rho's reasoning makes sense.

I don't use ON TIMER either, but you can make events happen at regular intervals regardless of what is happening in code, does it actually interrupt a sub? Might be useful in clock making.

[Jack002]

Its useful in games programming. Interrupts are kinda mysterious. Think of two or more programs running concurrently. I think about this hot wheel timer I want to write, the two events you can't miss are when the car enters the first gate, and when it enters the 2nd gate and how much time has elapsed. Basic alone might be too slow to see these events if you need accuracy to 1/1000th a second, interrupts can help with that.  I'm still not to where I have done one yet tho.

I'm sure the mind of a juggler appreciates them. So many tasks going on simultaneously :-)