From d5bf79850c0b3326f74015d9bb362a42bcf0dcaf Mon Sep 17 00:00:00 2001 From: Mark Date: Tue, 5 Jan 2021 16:11:41 +0000 Subject: [PATCH] Update micropython.md --- software/micropython.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/software/micropython.md b/software/micropython.md index 8de72a7..48abc5e 100644 --- a/software/micropython.md +++ b/software/micropython.md @@ -85,9 +85,9 @@ This is, in fact, what you're doing when you live-code using the REPL. However, MicroPython uses a combination of compilation and interpretation techniques to run your program. Here's how: -When MicroPython sees a script it parses each line of the script. The end result is a set of in-memory tokens grouped in such a way that they represent how your program works. This is called the *parse tree*. +When MicroPython sees a script it parses each line of the script. The end result is a set of in-memory tokens grouped in such a way that they represent how your program works. This is called the *Abstract Syntax Tree (AST)*. -The parse tree is compiled into a terse set of instructions called Python *bytecode*. Bytecode instructions are like CPU assembly language instructions, but they are targeted for a *virtual machine*, not for a real piece of computer hardware. +The AST is compiled into a terse set of instructions called Python *bytecode*. Bytecode instructions are like CPU assembly language instructions, but they are targeted for a *virtual machine*, not for a real piece of computer hardware. The Python bytecode is given to the Python virtual machine to run and so your program is executed.