The fascinating story of Python (iii)

What exactly does the softchip architecture bring to developers? What is the difference between a traditional development routine and a conventional one?

It is believed that some developers have a basic understanding after reading the first two articles.

Here to explain the author's personal views, for reference only.

Formally,softchip has developed a restrictive design specification for the module, and the modules are deeply hidden, and the modules are no longer free to call the methods of other modules.

In fact, this seemingly restrictive action has completely liberated the module. Strictly speaking, the module designers are completely liberated. Why is it?

1. You no longer have a relationship with countless modules, you only deal with a character called Machine.

2, you do not know and no longer care what modules in the system and you work together, you only know what the API and the Eventbetween you and machine.

3, you in the coding period and the compiler does not need to tilt anyone to snort, you are free to write your own code.

4. When you need to debug, you can mock out any of the APIs and Event you need to match your own debugging.

You lose a few modules of the handle, instead, you have the entire machine, the condition is to have the standard!

In such a scenario, the developer is no longer involved in the other modules, concentrating on their own things.

Each module can focus on its own business.

most modules focus on specific work, and some of the modules stand Plan API and event allocations at a global or middle level.

This is the essence of hierarchical, modular design. the complexity of the whole system has been greatly reduced, and the improvement of quality and efficiency is a natural thing.

In the field of software development, this effect seems to be wild desires, but look at the hardware field, in fact, is already commonplace.

For example, a PC's NIC, which acts as a component, only needs to be plugged into the motherboard's PCI slot.

It does not need to know that the data it is going to send is an address from a memory strip outside of 10cm.

The memory bar, as another component, simply plugs into the memory slot of the motherboard and does not need to know that its data is being sent to the network via another chip outside of 10cm.

Well, who knows? Machine know, as machine specific image representative of board know, this is enough!

Therefore, the design of the network card does not need to know the memory of the things, the same, the memory of the designers do not need to know the graphics card things, we all just need to fulfill their own and machine interface between the agreement, this is enough!

softchip Description is beautiful, the code is very beautiful, but someone questioned: "Are you telling the truth?" Can it be achieved? ”

Is the most critical softchip code written? At this time, Python finally awaited to play.

It can be said that Softchip is born for Python tailor-made, not her mo! In turn, only Python can host softchip.

Python language features that are critical to the softchip architecture include:

Perfect Oop,duck typing, variable parameter mechanism, function/method pointer, dict/list data structure.

These language features, which are seen in a single language, are found in many languages, but when you put them all together, who else would be able to contend with it, except for Python?

C provides powerful pointers, but lacks all the other elements.

C + + has OOP, but it has no type-independent dict/list and cannot get a non-static method pointer.

The pointer in Java no longer exists ...

In the next article in this series, we will discuss the design and implementation of the critical softchip itself.

The fascinating story of Python (iii)