12-01-2022, 08:53 PM
(12-01-2022, 07:54 PM)James D Jarvis Wrote: CALL is an artifact of multi-module programming isn't it? Technically our programs aren't multi-module anymore. I suppose it would make sense if we were using some sort of DLL and we thus had to CALL the functions/routines in the linked library.
It's almost as old-fashioned as using LET.
Well now I feel old and no longer want pudding. All I can say is, don't LET the CD-Tray hit you in the ASCII on the way _OFFSET!
When I don't use CALL as an identifier, I sometimes place a blank space between a sub or function call, or a gosub statement. When I see a break in the lines of code, I know the flow is branching off to another routine. It's sort of a vertical identifier, much as indentation helps to identify conditional statements and loops.
Pete
CALL OBSOLETE (Wasn't that an MS-DOS routine?)