Source header for 'ZX_SOURCES_LIBRARY'

Hi, All. Here is a draft version of the subzha. Without this little thing there is no It makes no sense to classify and collect ASSM subroutines at all. The project is led by: Alexander Mayorov (Mas), Evgeniy Golyakov (Spencer), Dmitry Nesmachny (Merlin), you are God himself. The goal of the ZX_SOURCES_LIBRARY (ZSL) project is: 1. Collection of low-level subroutines (p/p) in Z80 assembler; 2. Systematization of items by thematic sections of the library; 3. Sorting similar items within a section by length/speed; 4. Working in FAQ-server mode (with addresses in zxnet/fidonet) It is supposed to automatically parse the sorts based on these header fields. Where there are two lines of dots, n lines can be used. ═══ CUT ═══ Name:........................................................................ Autr:........................................................................ Date:................................ Assm:............................ Info:........................................................................ Link:........................................................ Size:............................ Memo:............................ Takt:............................ IN:................................................................ OUT:........................................................................ Unpb:........................................................................Data:........................................................ ═══ EOF ═══ Now in more detail about each point: ═══ CUT ═══ Name: -name, which is also the call label of this sub-number from others, which will be used for assembling a project from disconnected sub-plots, placed in different thematic sections. In the body of the program this label must specify its first byte. Autr: -author of the subroutine and preferably e-mail address Date: - date of creation of the item (dd/mm/yyyy) Assm: -assembly editor, preferably indicating the version Info: - a brief description of the item in a few lines Link: -names of other called items from this one, separated by commas or starting on a new line, perhaps this is the field that FAQserver will use to send the entire project, if request for its component Size: -full size before installation Memo: -full working size with all variables and buffers Takt: - speed in processor cycles of all branches of the subdivision separated by commas or from a new line, of course, if the number of branches is small IN: -required input parameters OUT: -state of output registers Unpb: -undocumented commands are better written in the form: mnemonic/#hex code/analogue on documented commands or description of the impact on flags, registers, cells, ports. Data: - description of the variables, arrays, buffers used. Indicate which are temporary and which are not. Maximum stack depth. And other information that makes the process of interaction easier.═══ EOF ═══ This version of the subzha is made taking into account your wishes, which I'm still collecting. This hat will mark the beginning of each procedure, placed in the library, therefore, as they say, it’s not too late, coders/programmers, make an effort to understand the text. posted in CODE.ZX crossposted in REAL.SPECCY Thank you for your attention.