10-27-2025, 04:29 AM
(This post was last modified: 10-27-2025, 04:31 AM by ahenry3068.)
(10-27-2025, 01:48 AM)bplus Wrote: Well hell! I'm not going to argue with an assembly programmer.I like doing a lot of different stuff. And I'm not a wizard. The assembly I have been doing is 8 bit these days (I have done x86 in the distant past).
I do know I would never recommend QB64 to a Computer Scientist because they would learn so many bad habits! and be so mocked by their cohorts for programming with line numbers.
WTH? calling a varaible set by a Function at Run time a Const what were they thinking??? What sacrilege!
And we wont even get into GoTo
@ahenry3068 what are you doing hanging out here? are you slumming? LOL
And Charlie. I wasn't putting you down or trying to get into a huge existential argument. But to me compiler terminology has to mean something. And CONSTANT is a concept that transfers across a lot of different compilers. I've been dealing with some old development methods where they aren't available to me (Commodore BASIC
) and I use variables that I don't change for the same purpose in my code. But I make sure that when I'm discussing my code on those boards that I use the term **Psuedo Constant** for what I'm doing. And it helps me keep it straight in my own head.BTW Assembly code is actually why I don't have a problem with BASIC GOTO . Assembly doesn't have anything like SELECT CASE or IF THEN ELSE . It has a CALL and conditional and unconditional branch instructions. (I'm generalizing a lot, different CPU's have different instruction sets) To program in assembly you certainly must be prepared to deal with GOTO
