Source header for 'ZX_SOURCES_LIBRARY'

Hi, All.

Here is the draft version of the subzha. Without this little detail, 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 and the Lord 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 sorts based on these header fields.
Where there are two lines of dots, you can use n lines.

═══ CUT ═══
Name:..................................................
Autr:...................................................
Date:..................................
Assm:..................................

Info:.........................................................
........................................................
Link:........................................................
.....................................................

Size:................................................
Memo:..................................
Takt:..................................

IN:.........................................................
...............................................................
OUT:...............................................................
...............................................................
Unpb:.........................................................
...................................................
Data:.........................................................
....................................................
═══ EOF ═══

Now more details about each item:

═══ CUT ═══
Name:
-name, it is also the call label of this sub-p/n from others that will be used for
assembling a project from separate sub-sections,
placed in different thematic sections. In the body of the program
this label should indicate its first byte.

Autr:
- the author of the subroutine and preferably the e-mail address

Date:
- the date of creation of the subprogram (dd/mm/yyyy)

Assm:
- the assembler editor, preferably indicating the version

Info:
- a brief description of the subprogram in several lines

Link:
- names of other called items from this one, separated by commas or withnew line,
perhaps it is precisely this field that FAQserver will send the entire project when
requesting its component

Size:
- full size before installation

Memo:
- full working size with all variables and buffers

Takt:
- size in processor cycles of all branches separated by commas or
with a new line, of course, if the number of branches neviliko

IN:
- required parameters at the input

OUT:
- state of the registers at the output

Unpb:
- undocumented commands are better written in the form:
mnemonic/#hex code/analogue on documented commands or a description of the influence on
flags, registers, cells, ports.

Data: - description of the variables used, arrays, buffers.
Indicate which are temporary and which are not. Maximum stack depth.
And other information that facilitates the process of interaction between subsystems.
═══ EOF ═══

This version of the subzha is made taking into account your wishes, which
I am still collecting. This header will crown the beginning of each procedure
placed in the library, so, as they say, before it’s too late,
coders/programmers, make an effort and delve into the text.

Thank you for attention.

June 10, 2001 (and it was 03:02 then)
Evgeny Goljakov wrote in his letter to All:

EG> Here is the draft version of the subzha. Without this little thing, it makes no sense
EG> to classify and collect ASSM subroutines at all.

EG> The project is led by:
EG> Alexander Mayorov (Mas), Evgeniy Golyakov (Spencer),
EG> Dmitry Nesmachny (Merlin), you are the Lord God himself.

There is a proposal for this project to create a saecial echo. IMHO, each
subprogram will cause controversy and a desire to improve some individual places. And through the echo, with the help of many people, it will be honed to perfection. As a
precedent, I will cite Misha Zharov’s printing machine.

Vega / ex-Style Group. June 11, 2001

EG> Here is a draft version of the subzha. Without this little detail, it makes no sense
EG> to classify and collect ASSM subroutines at all.
EG> The purpose of the ZX_SOURCES_LIBRARY (ZSL) project is:
EG> 1. Collection of low-level subroutines (subroutines) in Z80 assembler;
EG> 2. Systematization of subroutines by thematic sections of the library;
EG> 3. Sorting of similar types subsection within the section by length/speed;
EG> 4. Working in FAQ-server mode (with addresses in zxnet/fidonet)
probably a good start, but a similar project has long been carried out by Faster/TNL from
Ulyanovsk. It would be nice for you to contact him.

I was with you. └└─┘┴ ┴└└─┘
j...@mail.ru

Where should the procedures be sent? Otherwise I have several
interesting procedures lying around here, maybe someone can speed it up.

On this note. Bye, Evgeny!

[CGE] [ARTVIEW] [THE KNIGHT'S ARENA] [IF GAME]
to be continued ...

NEWART/n-Discovery/SPb * Coder, gfx artist, AY music's fanat

Evgeny Goljakov ==========> All:

EG> Here is the project version of the subzha. Without this little detail, it makes no sense
EG> to classify and collect ASSM subroutines at all.
skip/

Good idea, I fully support it. I will try to provide
several procedures in the near future.

Bye!
Pa...@nm.ru rscg.boom.ru [RC 2.0 70%] [ZX] [Real Software]

EG> Name:
EG> -name, it is also the label for calling this subsection from others, which
EG> will be used to assemble a project from disconnected subsections,
EG> placed in different thematic sections. In the body
EG> of the program
EG> this label should indicate its first byte.

You see, asm and si are different things. A subroutine can have more than one
entry point. So this nasty thing cannot be a label, unless for
identification in the database, the input points need to be identified somehow, keeping in mind that there can be many of them.

EG> Link:
EG> -names of other callable items from this, separated by commas or with
EG> a new line, perhaps this is the field FAQserver
EG> will send the entire project when requesting it component

Hmm, but apparently the name will have to be specified with the path? There is no guarantee that there will be only one file with the name "MY BEST PROGRAM" in the database. Or somehow
resolve conflicts, for example: if such a name already exists, then change the last
byte and the links to this file that came with it, also rename... But
this is somehow complicated and clumsy... Some other way is probably necessary...

EG> mnemonic/#hex code/analogue on documented commands or
EG> description of the influence on flags, registers, cells, ports.

EG> Data: -description of usedvariables, arrays, buffers.
EG> Indicate which are temporary and which are not. Maximum depth
EG> of the stack.
EG> And other information that facilitates the interaction process
EG> p/p.

Sincerely, Dmitriy.

SK> Where should I send the procedures? Otherwise, I have several
SK> interesting procedures lying around here, maybe someone can speed it up.

It is supposed to take subsections of all assemblers into the library,
but ONLY when filling out the subzh placed at the beginning
of the text. So as not to drown in the avalanche of chaos of sorts.

While we are talking about the margins of the hat, where to send - later.

SK> NEWART/n-Discovery/SPb * Coder, gfx artist, AY music's
SK> fanat
Thank you for your attention.

VS> There is a proposal for this project to create a saecial
VS> echo. IMHO, each subprogram will cause controversy and a desire
VS> to improve some individual places. And through the echo, with the help of many people, it will be honed to perfection. As a precedent, I will cite Misha Zharov's printer.

The theme of the echo CODE.ZX is completely suitable for this.

Gentlemen, we have moved away from the sub...

VS> Vega / ex-Style Group. June 11, 2001
Thank you for your attention.

DN> Hmm, but apparently the name will have to be specified with the path? There is
DN> no guarantee that there will be only one file named "MY BEST PROGRAM"
DN> in the database. Or somehow resolve
DN> conflicts, for example: if such a name already exists, then change
DN> the last byte and the links to this file that came with
DN> also rename it... But this is somehow complicated and
DN> clumsy... Some other way is probably necessary...

Just require the uniqueness of subnames from those sending them

Thanks for attention.