Z80 timing

That extension is great - I've been using it all the time! The only thing I miss is to be able to add my own macros. It would have been great if it could have understood macros

It's just that it does not add the extra MSX-wait states. That is a bit annoying.

And then there is even more to it. When you work with the VDP, depending on the MSX Engine used, the I/O delay varies. 0, 1 or 2 extra wait states: https://www.msx.org/wiki/Toshiba_T9769#Differences_between_r...

Soo, all in all, a bit complex thing.

Hi, Bengalack!
Instruction detection is line-based, and symbols and expression are not actually evaluated so adding proper macro support would require a complete rewrite (it would be a complete assembler rather than the simple parser it is now into)...
However, I did some internal improvements to support SjASMPlus alternative syntax and fake instructions, and I think that code can be used to support simple user-defined macros.
If re-defining those macros in your settings.json is acceptable (like this line, for example), please open a github issue (or this thread, or an email, etc.) with a couple example macros and I'll take a look at it!
I'm afraid that reading the macros from the actual sources is beyond my VSCode-extension-coder-newbie skills :_D

This extension is the first thing I coded something in TypeScript and, to be honest, I even don't know if TypeScript can be used to create command line utilities :_D.
Beside selecting the text and reading the configuration from settings, the code its pretty straightforward so it should be easy extract the relevant parts (to create a TypeScript cli tool) or migrate it to another language (such as Java). Code is here, btw.
Please take a look at Reidrac's z80count and Santi Ontañon's mdlz80optimizer as they may suit better this particular scenario (z80count may be easier to convert to cli, and mdlz80optimizar maybe already have a "report" on the original source code time/size).

I tried MDL (I am already trying to include it into the MSXgl build chain) but I didn't found a way to get global statistics. With -asm+ I can get line by line timing and size but not global ones.

I'll try z80count.

Being able to generate a report on timing and code size per function and per file, would be really great.