|
Call by reference / value
|
11-27-2023, 11:19 PM
Just as long as everybody remembers each parameter is passed to a subprogram by reference. It means the value of a variable could be changed accidentally. BYVAL cannot be used away from DECLARE LIBRARY block, and therefore there is no easy way to do anything about it except to declare local variable copies that protect the incoming parameters.
|
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
Call by reference / value - by Kernelpanic - 11-27-2023, 07:54 PM
RE: Call by reference / value - by mnrvovrfc - 11-27-2023, 11:19 PM
RE: Call by reference / value - by SMcNeill - 11-28-2023, 02:36 AM
RE: Call by reference / value - by TerryRitchie - 11-28-2023, 03:41 AM
|
| Possibly Related Threads… | |||||
| Thread | Author | Replies | Views | Last Post | |
| How Many Years Until QB64ers are CALL OBSOLETE? | Pete | 62 | 3,997 |
02-20-2026, 03:15 AM Last Post: bert22306 |
|
| You never CALL | Pete | 13 | 2,484 |
12-02-2022, 12:23 AM Last Post: mnrvovrfc |
|
| Call a video from QB64 | Kernelpanic | 3 | 928 |
09-02-2022, 05:35 PM Last Post: Kernelpanic |
|
| Variable as a reference or value to a function | Kernelpanic | 22 | 4,380 |
08-08-2022, 07:41 PM Last Post: bplus |
|
| Confusion over passing by reference vs passing by value | hanness | 12 | 2,778 |
06-19-2022, 10:58 PM Last Post: DSMan195276 |
|
