SjASMPlus от z00m

[NEO SPECTRUMAN]

Ped7g, а можно добавить режим
чтоб при перезаписи выдавались предупреждения?

чтоб такой код

 org $C000
xor a
xor b
xor c
xor d

 org $C001
xor e

выдавал
warning $C001 was overwriten


ну и если не заводить отдельный массив для этого
то хотя бы проверять на $00 перед записью

nop-ов не так много в коде
и лучше хоть какая то проверка чем никакой...

[Advertiser]

[Ped7g]

Current status: no such feature

Future:
- not as default for sure, because there are projects using the pattern of device memory re-use to build different binary blocks at the same position (savebin/savetap between).
- as option: possible... sounds like some work, to develop some simple and fast code for it, as there is no simple test (except having usage-bitmap for whole device memory, but that sounds ugly. But maybe there is some other way, maybe some lists of ranges and checking for overlaps.
- workaround: use less `ORG`, use more `ds/align` to advance to next block of code, use ASSERT or MMU with "w" or "e" mode to guard you against making current section bigger than what you expected, etc...

But it sounds like non-trivial thing to add, and also you should be able to work-around it with ASSERT quite well. Switching one option ON would be even better, but doesn't feel to me like critical feature needed ASAP.

But I will keep it on mind... (maybe add enhancement-issue on github so I don't forget about it )

[NEO SPECTRUMAN]

- not as default for sure

это нужно только для отладочных проверочных целей
так как не всегда ясно правильно ли все расположено в памяти или нет
а проверить нет возможности

у меня 100% org-ов генерируется при помощи lua
а на сколько это правильно происходит в сочетании с макросами переменной длинны не ясно

- - - Добавлено - - -

use more `ds/align`

они не рационально расходуют память

[NEO SPECTRUMAN]

вот такая ошибочная конструкция не выдает ошибку и не генерирует никакой код

	macro test
	test
	endm

	org $8000
	test

все что видно на экране

SjASMPlus Z80 Cross-Assembler v1.18.0 (https://github.com/z00m128/sjasmplus)

и найти эту ошибку трудно


с таким же успехом не работает такой не правильный код

	macro exx
	exx
	endm

	org $8000
	exx

а вот такая конструкция прекрасно рабоатет

	macro EXX
	exx
	endm

	org $8000
	EXX

я длительное время подобным пользовался и даже не замечал что это зацикленный макрос

[Ped7g]

For stuff like this - intentionally wanting to substitute legal instruction by your own macro:

	macro exx
	; exx    ; infinite cycle
         @exx  ; Z80 exx, avoiding infinite cycle of macro calling
	endm

you can use the "@" operator to prevent macro matching, ie. `@exx` inside macro definition to do real Z80 `exx`, and in your code you can then:

    exx  ; does the macro
   @exx ; does the Z80 exx even if "exx" macro exists

The error messages and state recovery in case of infinite loops in DEFINE/MACRO definitions is really bad, sometimes it will raise max-nesting limit, sometimes it will just crash the assembler - I know about it, but I have currently no mood to work on this stuff

	macro test
	test
	endm

	org $8000
	test

^^ this needs just few changes to be legit code, for example:

	macro test
nesting = nesting - 1
        IF 0 < nesting
	test
        ENDIF
	endm

	org $8000
nesting = 4
	test

^^^ this is valid source, and will compile fine, but I don't see how you would consider it "different" from yours infinite example (except hitting some guardian-value to notice it's in cycle too much).

So it's not so easy to guard against it... there are some protections in sjasmplus which should catch infinite substitutions and loops, but they are not working that good at this moment, sorry. There's a room for improvement in this area, I agree.