Sony, I didn't get a chance to try this release yesterday.tvrfan wrote: ↑Mon Dec 16, 2019 2:34 pm Posted 4.0.2 with following fixes
1. TEMP - sub command will ignore any extra parameters (symbol name should work)
2. TEMP - removed and ignore bank commands - not normally required anyway
3. Fixed problem with incorrect number of arguments (CARD and others)
4. Fixed problem with listing displaying incorrect number/symbol in indexed opcodes
5. Fixed 'NULL' symbol with word commands
6. Added more code to correctly size arguments. (was missing check when argument used as an address -> should fix CARD issue)
7. Fixed crash when commands overlap or fail - now gives error message instead
8. Fixed Windows path bug. Found when debuggung for the others.... causes processing to stop.
You just know I want to override it with my own naming convention, that includes the address.Also now prints a special func number for lookups - this will be basis of a new command setup (sorry JSA!)
Ok, the sooner the better.The variable argument changes meant BIG changes to subroutines, and honestly I haven't worked out how to allow user commands
along with the variable detect. This obviously needs to be done at some point.
I think numbers just obfuscate. Result is just another document to look up.Also I want to change the commands to make sizes simpler. instead of :S Y: Y: (or : SW : SW) layouts, I want your opinion on -
:Z n : where Z is siZe. n = 1 unsigned byte, 2 unsigned word, 3 unsigned long, 5 signed byte, 6 signed word, 7 signed long.
(this is actually what the code uses inside the program.)
A convention already exists with names for function look ups and output code. Consistency is good.
mmmm, NO, I don't want to see 16FunLU1 or 3R4c <<=1
I think it is simpler to maintain a consistent convention, who's pattern becomes instantly recognized.
For the sake of change or tracking values;
:UB or :UY
:SB or :SY
Does that negate the need for Z:
Today's release crashes with my dir. I will let you know what I find.