Відео

❤❤❤😊

Great explanation, another example is for opening files, you try to open a file and check whether it's open. The scope will be inside the if, if something crashes inside that if; it will close that file automatically, it's basically RAII. And you don't have to close the file, because that will be done automatically when exiting the if.

Geeky too lost in the trees to see the forest. As if an alien asked a human what "breakfast" was, and the human handed them a recipe for an omelet. What a person wants to know when asking what a compiler is, isn't how it does what it does, but why it does what it does. The first thing to explain would be that computer chips process linear streams of ones and zeros, what is called binary code.So, something must happen to the text written in a computer language to transform it into a binary sequence of ones and zeros. But it's more than that of course, as a computer chip can only handle binary sequences where the ones and the zeros are organized in one particular way. Computer chips are extremely even terminally intolerant of sequences nor ordered in particular patterns. A compiler is a translation layer that converts a program wittten as text in one particular programming language, into the exact binary sequence structure that a given processing chip can execute, can process, can transform into some desired output. Yes, this video explains how most current compilers go about doing that translation, but the really interesting part of all of this is that compilers have become sophisticated in ways that make them the essential core base component of the evolution of computers and computing. Compilers are written as manifestations of compiler theory, and this theory is general enough to drive the design of computer chips on one end, and programming languages on the other end. A compiler is something akin to theoretical physics, describing and formalizing the structure and behavior of computation itself. This should not be surprising, people who translate text from one language to another often understand language better than those who only speak one language. When Einstein eloquently related energy, time, mass, and velocity, he made us more able to understand any one of these factors better even when isolated. Interestingly, one can write faster compilers or one can write compilers that expose their own process for examination. You can't have booth. On another axis, you can write a more efficient compiler if it only translates from one programming language to one processing chip architecture. If you want a compiler to work between any programming language and any chip architecture, your compiler will be larger and slower. Or, you can make your chips simple, building them up as grids of a great many self same units, and you can create compilers that convert any type of processing problem into units that can be processed on a grid of self same processing units, you can make the computational topology flat, and fast, by slowing down the translation process, the compiler, even though doing sow will result in longer binary compiled code, the chip may at times process the compiled code faster. There are chips that look ahead at the incoming stream of binary and reconfigure themselves optimally for that particular stream of compiled binary. There are language/compiler pairs written to particular types of problems, to math heavy problems, to text heavy problems, to spacial geometry problems, to machine language AI problems, to pattern recognition, to prediction problems, etc etc etc.

❤❤❤😊

"I dunno, just try them both 🤷‍♂️ thanks for the click" 🤦‍♂️

Learning to code is good, even if for no other reason than knowing how programs work and that it's really just a pile of numbers and not magic.

❤❤❤😊

How do you add the colored subtitle animations to your shorts?

This is fasctinating and insane to me at the same time, how do people get hang of this low level stuff, seems beyond my comprehension.

Well done 👏