Host Engineering Forum
General Category => Do-more CPUs and Do-more Designer Software => Topic started by: RBPLC on August 31, 2019, 09:43:58 AM
-
In the first scan I'm trying to define string variables. I tried this with the COPY command but get errors when trying to enter my strings as text into the source field. What is the proper way to write a string to a variable to define it?
-
We probably should look at adding a string option to INIT, but I guess the best way is STRPRINT.
-
Thanks Bob. I would recommend something like INIT or COPY so that many of these can be defined in one instruction.
-
I've often wondered just what the difference is between INIT and COPY. And MAPIO and COPY. Why would one use MAPIO when COPY lets you do ranges of elements?
-
I've often wondered just what the difference is between INIT and COPY. And MAPIO and COPY. Why would one use MAPIO when COPY lets you do ranges of elements?
COPY and INIT are both "macros" (along with CALL). COPY was developed later once we had a better set of "data assignment" instructions. COPY really should be the one stop shop for 90% of your data assignments. One of its limitations is string literals - you still have to use STRPRINT for that. We can definitely look at addressing that in the future.
-
You have my vote for adding string initializations to Init
-
You have my vote for adding string nationalizations to Init
I was planning on doing it for COPY, but if we do what I want to do, I should also be able to add it to INIT also. TomAYto TomAHto. One person's INIT instruction is another person's COPY instruction.
-
Thanks. I use INIT much more often that COPY so I'd find that very useful.
-
COPY is a superset of INIT. It can do everything INIT does, plus what MOVER and MEMCOPY can do.
-
I have pretty much standardized on using INIT in my initialization stages.
-
I like the idea of adding literals to INIT, we'll just need to see how much it takes.