SjASMPlus от z00m

[Ped7g]

все равно метки получаются плохо различимыми

yes, doesn't look well.

I would maybe try to use the CN ahead of instruction, and real labels on separate line ahead:

frq = $+1
CN=CN+10 :   ld de,$0123

BTW, the "=" (alias "DEFL") is more like variable, and allows redefinition of the value. If things like `frq` are used for self-modify code, I would suggest to use EQU instead, which creates "constant" (attempt to redefine it second time in source will emit error about different value assigned).

With a bonus of the EQU maybe creating different visual feel in this case too:

frq EQU $+1
CN=CN+10 :   ld de,$0123

Or maybe use macro? But that will explode the listing file, but if you are not planning to use listing very often for this area of code, it may help with the source (you can disable listing for particular part of source, if you are using listing to check other areas).

countT  MACRO   cycles?
CN=CN+(cycles?)
        ENDM

CN=0
        ld      a,b         : countT 4
        and     $70         : countT 7
frq=$+1 ld      de,$1234    : countT 10
        IF CN < 26
            .((26-CN+3)/4) nop
            countT (26-CN+3)&-4
        ENDIF

[Advertiser]

[Grand]

Полезно и в восьмеричном виде выводить числовую информацию. Вспомните, байты атрибутов экрана нагляднее именно в восьмеричном виде.

[NEO SPECTRUMAN]

But that will explode the listing file

а он и так у меня обычно не читаемый и весит мегабайтов 7

например листинг NSID_Emu весит 15MB
туда давно бесполезно заглядывать...


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

Or maybe use macro?

интересно
возможно оно даже будет работать с adp

а на каком pass-е уже будет результат?
так как полученные цифры еще будут передаваться lua для расчета таблиц

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

you can disable listing for particular part of source, if you are using listing to check other areas).

а как это делать?

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

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

[Ped7g]

а на каком pass-е уже будет результат?
так как полученные цифры еще будут передаваться lua для расчета таблиц

Macros are like "includes", expanded upon instance in every pass (becoming part of source). Notice how inside my example macro "CN=CN+(cycles?)" -> the argument is in parentheses - that's because the macro arguments are substituted in C-preprocessor way, substituting the strings, doing the value evaluation as last step after all substitutions, so without parentheses the usage `countT (26-CN+3)&-4` does expand to `CN=CN+(26-CN+3)&-4` which will evaluate to different result as `CN=CN+((26-CN+3)&-4)`! So it's similar landmine field like C #defines ...

But the value of symbol CN is updated in every pass, just as if you would do the CN=CN+4 at beginning of line (but it happens after instruction, because macro is expanded after instruction).

---------------

listing disabling:
http://z00m128.github.io/sjasmplus/d...on.html#po_opt

    OPT push listoff    ; preserve current state of listing, and switch listing off
      ; some code without listing (only marked by "# listing disabled" and "# listing enabled" lines in listing)
      ...
    OPT pop              ; restore the listing to original state

(the disabling/enabling of listing is announced in the listing file, so this shortens listing for blocks of code, for single line this will explode listing even more)

the OPT state can be push/pop-ed, so you can even nest these in includes/etc... if the top level has listing enabled, and it will go through multiple nested blocks having this switch off, then the first will switch listing off, nested ones will make no visible change, and the final last `opt pop` will restore listing back to "on".

Similarly if you are doing sjasmplus library to be included as source code, and you want customize the syntax, but you don't want to affect project which is including your source, you can do `OPT push reset --syntax=aBf` to have your source going by these rules, then `OPT pop` at end of your library to restore the syntax of original project...

Sorry for spamming you with this info you didn't ask for, but I'm kinda proud of the OPT design... :P

[NEO SPECTRUMAN]

так намного лучше

[Bedazzle]

da, mozno. Tolko 8-bit ja dumaju?

Да, 8 бит хорошо.

(my Russian is too limited to make full sentence ... heh, sorry)

Your Russian is quite well written for the novice!

[NEO SPECTRUMAN]

for the novice!

может потому что Ped7g из Чехии
что как бы тоже exUSSR

[Black Cat / Era CG]

А еще язык славянский.

[NEO SPECTRUMAN]

Ped7g, а сейчас как то можно организовать синонимы для макросов?

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


по смыслу должно работать так

	macro aabb123 || blahblahblah_aa_bb_123_NOW111 aaa 
	defb aaa
	...
	100500 lines of code
	...
	endm

или так

	macro aabb123 || blahblahblah_aa_bb_123_NOW111 aaa 
	defb aaa
	...
	100500 lines of code
	...
	endm

	macro blahblahblah_aa_bb_123_NOW111 aaa 
	aabb123 aaa
	endm

с результатом

	aabb123 1

	blahblahblah_aa_bb_123_NOW111 2

	defb 1
	...
	100500 lines of code
	...
	defb 2
	...
	100500 lines of code
	...

при этом на всех PASS-ах
синонимы должны вести себя так же как и оригинальный макрос

define-ом наверно будет опасно пользоваться для такого
хотя надо будет попробовать

[Ped7g]

So you want the same macro, but with the two different names?

The second way should work quite ok?

	macro aabb123 aaa ; "main" version 
	defb aaa
	...
	100500 lines of code
	...
	endm

	macro blahblahblah_aa_bb_123_NOW111 aaa ; "alias" version 
	aabb123 aaa ; call the "main" version of macro
	endm

	; usage
	aabb123 1
	blahblahblah_aa_bb_123_NOW111 2

Is this broken for you?

DEFINE is of course another option, but that works best with distinct names, like `DEFINE blahblahblah_aa_bb_123_NOW111 aabb123` .. seems unlikely you will have collision with such long string like "blahblahblah_aa_bb_123_NOW111" (although may happen, if you have "blahblahblah_aa_bb_123_NOW111_2" -> "aabb123_2" will be substituted.