So

Hello Shaos For some reason I haven’t looked into the topic here for a long time, it was rolling peacefully here Here I have the following thoughts: Regarding calling methods, it was said in http://zx.pk.ru/showpost.php?p=32310&postcount=67 and many copies were broken in http://zx.pk.ru/showthread.php?t=1811 Therefore, as I understand it, the method of calling via RST is rejected and two methods remain - core (begins with a chain JP) and modular (begins with a table relocations). It is useless to argue about their necessity here, so we will accept them together. Regarding the call interface, you can use registers, stack, pointers. Each method has both advantages and disadvantages. And therefore each of they have the right to life - due to their specificity. I understand that it is impossible carry out data transfer with a pointer according to the Hitech-C interface, if this so it (maybe) needs to be improved. In general, my personal opinion is that the method passing information (stack or pointer) will ultimately have little effect on productivity (more/less). This is due to the fact that you will have to work in basically with the same data that is implemented (read/written) in general the same command systems, so the dispute regarding passing parameters is through stack or through a pointer - I also think it’s not significant. Now regarding libraries - they are needed in ANY CASE, Stanislav has already suggestedmethod - just try to write something completely primitive - on what In fact, the entire SDK system will be debugged. We set a goal - writing an SDK We set the task - debugging the SDK using the example of the game "Mine Mines" It is necessary to create the following procedures: - The procedure of sawing - if you successfully guess the mine during the explosion - Cursor processing procedure - the cursor is placed on top of the existing picture, remembers what he overwrites with himself and then (second call or call to a given point of the same procedure) restores the background - The procedure for drawing windows is not attribute drawing but full-fledged, assumption - no need to remember the background under the window - Procedure for printing text - printing text in a given window, the parameters are the width of the window and the height of the typed text - i.e. sentences text are automatically divided into words and if the words do not fit, then it transferred - The procedure for polling the keyboard and manipulators - mice and joysticks Variations of each of the discrete procedures above are accepted - please do not lay out the finished all-in-one. Conventions: Every procedure must be documented. Availability required examples of use (to implement the specified task).