Did this author be an programmer in ?
I don’t know what kind of group the readers of this book are. First of all, I introduce two basic framework settings:
1. Ghosts cannot be eliminated;
2. Only ghosts can fight ghosts;
to be honest, what attracts me the most until now is the collision between different rules and the setting of the worldview from the beginning.
The relationship between ghosts and ghost slaves of different types and levels is like the relationship between (parent class & subclass) in programming.
And those ghost-controlling people are like variables in code, such as randomly selecting the letter n as a variable and assigning values. At this time, this variable n contains a number, just like the ghost in the body of the ghost master in the early stage.
The lucky ghost driver survived through various methods and successfully merged multiple ghosts in his body to maintain balance, and could mobilize the ghosts in his body according to his own needs. It's like a (variable n) turns itself into an n[array], from representing a single number to a collection of numbers.
Some lucky ghost drivers can also call some built-in function tools for their own use, such as //Ghost Scissors (); Ghost Hatch ();
and even some tools have complex functions, can run stably for a long time, and have strong capabilities. Unlike an ordinary function, I have no doubt that some tools need to call specific libraries before they can be used, such as //#Ghost Bus; #Ghost Painting;
Even some powerful ghost drivers can assemble and package themselves into a library, and then develop functions for others to use on their own basis.
For example, Ghost Child //The latest version of Ghost Child has added the infinite clone function
For example, Coffin Nail //There is obvious signs of human development, and the functions are somewhat similar to the dead loop function while(1){}
For example, Yang Jian's Golden Trident //Good guy, he has directly made a weapon into a library. If any function is needed, it directly calls the corresponding function
—————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
library has function();
has [n array];
...
Maybe the so-called ghost puzzle is nothing more than collecting suitable ghosts and absorbing them into their own code, and finally forming a complete library. Those living libraries can improve themselves while becoming stronger, and can also upgrade and update their own libraries at any time. ——————————————
And those dead libraries have really become evil spirits. Often, these people are basically S-level disasters after death.
So those elderly people will try every means to suppress themselves before they die. There are only two ways.
One is to bury yourself, no one can find it. Eliminate or hide the possibility that the library itself is called.
The second type of
finds a way to dismember its library before death, reducing the degree of perfection of the library, thereby reducing the level of terror of ghosts.
For example, the headless corpse of the Caesar Hotel //This man developed a function that can dismember other libraries by himself, and then dismembered himself into shadows, body, head... suddenly messed up.
————————
In fact, now it seems that those strangeness of varying degrees are likely to be caused by the upgrade of different variables into libraries in the previous eras, and they lose control after death.
In short, as long as the initial rigorous setting is continued and the writing process is not off-the-scenes, then this book is simply a must-read book for programmers. After reading it for a long time, it can really cultivate logical thinking.
