diff --git a/_sources/GeneralIntro/ExperimentalDebugging.rst b/_sources/Debugging/ExperimentalDebugging.rst
similarity index 98%
rename from _sources/GeneralIntro/ExperimentalDebugging.rst
rename to _sources/Debugging/ExperimentalDebugging.rst
index 7a91ae8e..23b4e646 100644
--- a/_sources/GeneralIntro/ExperimentalDebugging.rst
+++ b/_sources/Debugging/ExperimentalDebugging.rst
@@ -8,7 +8,7 @@
License".
.. qnum::
- :prefix: intro-12-
+ :prefix: debug-1-
:start: 1
Experimental Debugging
@@ -46,7 +46,7 @@ practices.
**Check your understanding**
-.. mchoice:: question1_12_1
+.. mchoice:: question100_1_1
:answer_a: programming is the process of writing and gradually debugging a program until it does what you want.
:answer_b: programming is creative and debugging is routine.
:answer_c: programming is fun and debugging is work.
diff --git a/_sources/GeneralIntro/WhatisDebugging.rst b/_sources/Debugging/WhatisDebugging.rst
similarity index 97%
rename from _sources/GeneralIntro/WhatisDebugging.rst
rename to _sources/Debugging/WhatisDebugging.rst
index 1d8f80c9..5e297711 100644
--- a/_sources/GeneralIntro/WhatisDebugging.rst
+++ b/_sources/Debugging/WhatisDebugging.rst
@@ -8,7 +8,7 @@
License".
.. qnum::
- :prefix: intro-8-
+ :prefix: debug-2-
:start: 1
.. index:: debugging, bug
@@ -25,7 +25,7 @@ since. For more about this historic event, see `first bug <http://en.wikipedia.o
**Check your understanding**
-.. mchoice:: question1_8_1
+.. mchoice:: question100_2_1
:answer_a: tracking down programming errors and correcting them.
:answer_b: removing all the bugs from your house.
:answer_c: finding all the bugs in the program.
diff --git a/_sources/Debugging/toctree.rst b/_sources/Debugging/toctree.rst
new file mode 100644
index 00000000..b9ff397e
--- /dev/null
+++ b/_sources/Debugging/toctree.rst
@@ -0,0 +1,8 @@
+Debugging
+:::::::::
+.. toctree::
+ :caption: Debugging
+ :maxdepth: 2
+
+ WhatisDebugging.rst
+ ExperimentalDebugging.rst
diff --git a/_sources/GeneralIntro/ATypicalFirstProgram.rst b/_sources/GeneralIntro/ATypicalFirstProgram.rst
deleted file mode 100644
index 5145d725..00000000
--- a/_sources/GeneralIntro/ATypicalFirstProgram.rst
+++ /dev/null
@@ -1,72 +0,0 @@
-.. Copyright (C) Brad Miller, David Ranum, Jeffrey Elkner, Peter Wentworth, Allen B. Downey, Chris
- Meyers, and Dario Mitchell. Permission is granted to copy, distribute
- and/or modify this document under the terms of the GNU Free Documentation
- License, Version 1.3 or any later version published by the Free Software
- Foundation; with Invariant Sections being Forward, Prefaces, and
- Contributor List, no Front-Cover Texts, and no Back-Cover Texts. A copy of
- the license is included in the section entitled "GNU Free Documentation
- License".
-
-.. qnum::
- :prefix: intro-7-
- :start: 1
-
-A Typical First Program
------------------------
-
-Traditionally, the first program written in a new language is called *Hello,
-World!* because all it does is display the words, Hello, World! In Python, the source code
-looks like this.
-
-.. sourcecode:: python
-
- print("Hello, World!")
-
-This is an example of using the **print statement**, which doesn't actually
-print anything on paper. It displays a value on the screen. In this case, the result is the phrase:
-
-::
-
- Hello, World!
-
-Here is the example in activecode. Remember, activecode windows allow you to execute python
-code while inside the textbook. When you click **Run** you will execute whatever code has
-been written in the window. Each time you hit **Run** a new version of the code will be saved
-in that activecode window's history. If you have already run code in the activecode window
-before and would like to revert your code to a prior save, click **Load History** and a bar
-will appear. Your most recent code will be on the right side of the bar, and the first time
-you clicked **Run** will be on the left side. Regardless of whether you've run the window in
-the past though, once you start to execute code the **Load History** button will change to
-the history bar. If you would like to see how python processes your code step-by-step then
-click on **Show CodeLens**. If you have already opened CodeLens and would like to step
-through different code then you'll need to refresh the page. Give it a try!
-
-.. activecode:: ac1_7_1
-
- print("Hello, World!")
-
-The quotation marks in the program mark the beginning and end of the value.
-They don't appear in the result. You'll learn more about why in the next chapter.
-
-Some people judge the quality of a programming language by the simplicity of
-the Hello, World! program. By this standard, Python does about as well as
-possible.
-
-**Check your understanding**
-
-.. mchoice:: question1_7_1
- :answer_a: sends information to the printer to be printed on paper.
- :answer_b: displays a value on the screen.
- :answer_c: tells the computer to put the information in print, rather than cursive, format.
- :answer_d: tells the computer to speak the information.
- :correct: b
- :feedback_a: Within the Python programming language, the print statement has nothing to do with the printer.
- :feedback_b: Yes, the print statement is used to display the value of the thing being printed.
- :feedback_c: The format of the information is called its font and has nothing to do with the print statement.
- :feedback_d: That would be nice! But no...
-
- The print statement:
-
-
-.. index:: debugging, bug
-
diff --git a/_sources/GeneralIntro/Algorithms.rst b/_sources/GeneralIntro/Algorithms.rst
deleted file mode 100644
index cc7ba013..00000000
--- a/_sources/GeneralIntro/Algorithms.rst
+++ /dev/null
@@ -1,52 +0,0 @@
-.. Copyright (C) Brad Miller, David Ranum, Jeffrey Elkner, Peter Wentworth, Allen B. Downey, Chris
- Meyers, and Dario Mitchell. Permission is granted to copy, distribute
- and/or modify this document under the terms of the GNU Free Documentation
- License, Version 1.3 or any later version published by the Free Software
- Foundation; with Invariant Sections being Forward, Prefaces, and
- Contributor List, no Front-Cover Texts, and no Back-Cover Texts. A copy of
- the license is included in the section entitled "GNU Free Documentation
- License".
-
-.. qnum::
- :prefix: intro-2-
- :start: 1
-
-Algorithms
-----------
-
-An **algorithm** is a step by step list of instructions that if followed exactly will solve the problem under consideration.
-
-Our goal in programming is to take a problem and develop an algorithm that can
-serve as a general solution. Once we have such a solution, we can express
-it as a program and use our computer to automate the execution.
-These programs are written in **programming languages**.
-
-**Check your understanding**
-
-.. mchoice:: question1_1_1
- :answer_a: To think like a computer.
- :answer_b: To be able to write code really well.
- :answer_c: To be able to solve problems.
- :answer_d: To be really good at math.
- :correct: c
- :feedback_a: Computers do not think, they only do what we humans tell them to do via programs.
- :feedback_b: While it is necessary for most computer scientists to know how to write code, it is not the most important skill.
- :feedback_c: Programming is all about solving problems. We use computers to automate solutions to problems and to do things faster and more accurately than we can do by hand or manually.
- :feedback_d: Algorithmic thinking and mathematical thinking are in some ways similar. Practice at mathematical thinking will probably help in learning to program. But the content itself is different. You do not have to know a lot of math to be a good programmer.
-
- What is the most important skill for a programmer?
-
-.. mchoice:: question1_2_2
- :answer_a: A solution to a problem that can be solved by a computer.
- :answer_b: A step by step list of instructions that if followed exactly will solve the problem under consideration.
- :answer_c: A series of instructions implemented in a programming language.
- :answer_d: A special kind of notation used by programmers.
- :correct: b
- :feedback_a: While it is true that algorithms often do solve problems, this is not the best answer. An algorithm is more than just the solution to the problem for a computer. An algorithm can be used to solve all sorts of problems, including those that have nothing to do with computers.
- :feedback_b: Algorithms are like recipes: they must be followed exactly, they must be clear and unambiguous, and they must end.
- :feedback_c: Programming languages are used to express algorithms, but an algorithm does not have to be expressed in terms of a programming language.
- :feedback_d: Programmers sometimes use a special notation to illustrate or document an algorithm, but this is not the definition of an algorithm.
-
- An algorithm is:
-
-
diff --git a/_sources/GeneralIntro/Comments.rst b/_sources/GeneralIntro/Comments.rst
deleted file mode 100644
index 21dd72dc..00000000
--- a/_sources/GeneralIntro/Comments.rst
+++ /dev/null
@@ -1,66 +0,0 @@
-.. Copyright (C) Brad Miller, David Ranum, Jeffrey Elkner, Peter Wentworth, Allen B. Downey, Chris
- Meyers, and Dario Mitchell. Permission is granted to copy, distribute
- and/or modify this document under the terms of the GNU Free Documentation
- License, Version 1.3 or any later version published by the Free Software
- Foundation; with Invariant Sections being Forward, Prefaces, and
- Contributor List, no Front-Cover Texts, and no Back-Cover Texts. A copy of
- the license is included in the section entitled "GNU Free Documentation
- License".
-
-.. qnum::
- :prefix: intro-13-
- :start: 1
-
-Comments
---------
-
-As programs get bigger and more complicated, they get more difficult to read.
-Formal languages are dense, and it is often difficult to look at a piece of
-code and figure out what it is doing, or why.
-For this reason, it is a good idea to add notes to your programs to explain in
-natural language what the program is doing. These notes are called comments.
-
-A **comment** in a computer program is text that is intended only for the human
-reader - it is completely ignored by the interpreter.
-In Python, the ``#`` token starts a comment. The rest of the line is ignored.
-Here is a new version of *Hello, World!*.
-
-.. activecode:: ac1_13_1
-
- #---------------------------------------------------
- # This demo program shows off how elegant Python is!
- # Written by Joe Soap, December 2010.
- # Anyone may freely copy or modify this program.
- #---------------------------------------------------
-
- print("Hello, World!") # Isn't this easy!
-
-Notice that when you run this program, it still only prints the phrase Hello, World! None of the comments appear.
-You'll also notice that we've left a blank line in the program. Blank lines
-are also ignored by the interpreter, but comments and blank lines can make your
-programs much easier for humans to parse. Use them liberally!
-
-**Check your understanding**
-
-.. mchoice:: question1_13_1
- :answer_a: To tell the computer what you mean in your program.
- :answer_b: For the people who are reading your code to know, in natural language, what the program is doing.
- :answer_c: Nothing, they are extraneous information that is not needed.
- :answer_d: Nothing in a short program. They are only needed for really large programs.
- :correct: b
- :feedback_a: Comments are ignored by the computer.
- :feedback_b: The computer ignores comments. It’s for the humans that will “consume” your program.
- :feedback_c: Comments can provide much needed information for anyone reading the program.
- :feedback_d: Even small programs benefit from comments.
-
- What are comments for?
-
-
-.. note::
-
- This workspace is provided for your convenience. You can use this activecode window to try out anything you like.
-
- .. activecode:: ac1_13_2
-
-
-
diff --git a/_sources/GeneralIntro/Figures/compile.png b/_sources/GeneralIntro/Figures/compile.png
deleted file mode 100644
index e297f732..00000000
Binary files a/_sources/GeneralIntro/Figures/compile.png and /dev/null differ
diff --git a/_sources/GeneralIntro/Figures/compile.svg b/_sources/GeneralIntro/Figures/compile.svg
deleted file mode 100644
index f03b716c..00000000
--- a/_sources/GeneralIntro/Figures/compile.svg
+++ /dev/null
@@ -1,820 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-
-<svg
- xmlns:dc="http://purl.org/dc/elements/1.1/"
- xmlns:cc="http://creativecommons.org/ns#"
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
- xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
- version="1.1"
- width="460"
- height="62"
- id="svg3012"
- inkscape:version="0.48.0 r9654"
- sodipodi:docname="compile.svg"
- inkscape:export-filename="/home/dmitchell/thinkcspy/source/illustrations/ch01/compile.png"
- inkscape:export-xdpi="90"
- inkscape:export-ydpi="90">
- <sodipodi:namedview
- pagecolor="#ffffff"
- bordercolor="#666666"
- borderopacity="1"
- objecttolerance="10"
- gridtolerance="10"
- guidetolerance="10"
- inkscape:pageopacity="0"
- inkscape:pageshadow="2"
- inkscape:window-width="1280"
- inkscape:window-height="947"
- id="namedview3099"
- showgrid="false"
- inkscape:zoom="2.2711111"
- inkscape:cx="241.44525"
- inkscape:cy="25.166334"
- inkscape:window-x="0"
- inkscape:window-y="24"
- inkscape:window-maximized="1"
- inkscape:current-layer="layer1" />
- <defs
- id="defs3014">
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4644"
- is_visible="true"
- pattern="M 0,0 1,0"
- copytype="single_stretched"
- prop_scale="1"
- scale_y_rel="false"
- spacing="0"
- normal_offset="0"
- tang_offset="0"
- prop_units="false"
- vertical_pattern="false"
- fuse_tolerance="0" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4640"
- is_visible="true"
- pattern="M 0,0 1,0"
- copytype="single_stretched"
- prop_scale="1"
- scale_y_rel="false"
- spacing="0"
- normal_offset="0"
- tang_offset="0"
- prop_units="false"
- vertical_pattern="false"
- fuse_tolerance="0" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4636"
- is_visible="true"
- pattern="M 0,0 1,0"
- copytype="single_stretched"
- prop_scale="1"
- scale_y_rel="false"
- spacing="0"
- normal_offset="0"
- tang_offset="0"
- prop_units="false"
- vertical_pattern="false"
- fuse_tolerance="0" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4632"
- is_visible="true"
- pattern="M 0,0 1,0"
- copytype="single_stretched"
- prop_scale="1"
- scale_y_rel="false"
- spacing="0"
- normal_offset="0"
- tang_offset="0"
- prop_units="false"
- vertical_pattern="false"
- fuse_tolerance="0" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4628"
- is_visible="true"
- pattern="M 0,0 1,0"
- copytype="single_stretched"
- prop_scale="1"
- scale_y_rel="false"
- spacing="0"
- normal_offset="0"
- tang_offset="0"
- prop_units="false"
- vertical_pattern="false"
- fuse_tolerance="0" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4624"
- is_visible="true"
- pattern="M 0,0 1,0"
- copytype="single_stretched"
- prop_scale="1"
- scale_y_rel="false"
- spacing="0"
- normal_offset="0"
- tang_offset="0"
- prop_units="false"
- vertical_pattern="false"
- fuse_tolerance="0" />
- <inkscape:path-effect
- effect="spiro"
- id="path-effect3148"
- is_visible="true" />
- <inkscape:path-effect
- effect="spiro"
- id="path-effect3136"
- is_visible="true" />
- <filter
- x="-0.5"
- y="-0.5"
- width="2"
- height="2"
- color-interpolation-filters="sRGB"
- id="filter3288">
- <feGaussianBlur
- result="result1"
- stdDeviation="0.01"
- id="feGaussianBlur3290" />
- <feBlend
- in2="result1"
- mode="multiply"
- result="fbSourceGraphic"
- id="feBlend3292" />
- <feTurbulence
- result="result3"
- numOctaves="3"
- seed="0"
- type="fractalNoise"
- baseFrequency="0.8"
- id="feTurbulence3294" />
- <feDisplacementMap
- in2="result3"
- scale="50"
- xChannelSelector="R"
- yChannelSelector="G"
- in="fbSourceGraphic"
- result="result2"
- id="feDisplacementMap3296" />
- <feMorphology
- result="result4"
- operator="dilate"
- radius="1"
- id="feMorphology3298" />
- <feBlend
- in2="result2"
- mode="screen"
- id="feBlend3300" />
- </filter>
- <filter
- color-interpolation-filters="sRGB"
- id="filter4280">
- <feGaussianBlur
- stdDeviation="3"
- result="result1"
- id="feGaussianBlur4282" />
- <feBlend
- in2="result1"
- mode="multiply"
- in="result1"
- result="result5"
- id="feBlend4284" />
- <feGaussianBlur
- stdDeviation="1"
- result="result6"
- in="result5"
- id="feGaussianBlur4286" />
- <feComposite
- in2="result5"
- operator="xor"
- in="result6"
- result="result8"
- id="feComposite4288" />
- <feComposite
- in2="result8"
- operator="xor"
- in="result6"
- result="fbSourceGraphic"
- id="feComposite4290" />
- <feSpecularLighting
- specularExponent="55"
- specularConstant="2.20000005"
- surfaceScale="2"
- lighting-color="#ffffff"
- result="result1"
- in="fbSourceGraphic"
- id="feSpecularLighting4292">
- <fePointLight
- z="20000"
- y="-10000"
- x="-5000"
- id="fePointLight4294" />
- </feSpecularLighting>
- <feComposite
- in2="fbSourceGraphic"
- operator="in"
- in="result1"
- result="result2"
- id="feComposite4296" />
- <feComposite
- in2="result2"
- operator="arithmetic"
- k1="0"
- k2="2"
- k3="1"
- k4="0"
- in="fbSourceGraphic"
- result="result4"
- id="feComposite4298" />
- <feComposite
- in2="result4"
- operator="in"
- result="result91"
- id="feComposite4300" />
- <feBlend
- in2="result91"
- mode="darken"
- id="feBlend4302" />
- </filter>
- <filter
- color-interpolation-filters="sRGB"
- id="filter4329">
- <feGaussianBlur
- stdDeviation="3"
- result="result1"
- id="feGaussianBlur4331" />
- <feBlend
- in2="result1"
- mode="multiply"
- in="result1"
- result="result5"
- id="feBlend4333" />
- <feGaussianBlur
- stdDeviation="1"
- result="result6"
- in="result5"
- id="feGaussianBlur4335" />
- <feComposite
- in2="result5"
- operator="xor"
- in="result6"
- result="result8"
- id="feComposite4337" />
- <feComposite
- in2="result8"
- operator="xor"
- in="result6"
- result="fbSourceGraphic"
- id="feComposite4339" />
- <feSpecularLighting
- specularExponent="55"
- specularConstant="2.20000005"
- surfaceScale="2"
- lighting-color="#ffffff"
- result="result1"
- in="fbSourceGraphic"
- id="feSpecularLighting4341">
- <fePointLight
- z="20000"
- y="-10000"
- x="-5000"
- id="fePointLight4343" />
- </feSpecularLighting>
- <feComposite
- in2="fbSourceGraphic"
- operator="in"
- in="result1"
- result="result2"
- id="feComposite4345" />
- <feComposite
- in2="result2"
- operator="arithmetic"
- k1="0"
- k2="2"
- k3="1"
- k4="0"
- in="fbSourceGraphic"
- result="result4"
- id="feComposite4347" />
- <feComposite
- in2="result4"
- operator="in"
- result="result91"
- id="feComposite4349" />
- <feBlend
- in2="result91"
- mode="darken"
- id="feBlend4351" />
- </filter>
- <filter
- x="-0.5"
- y="-0.5"
- width="2"
- height="2"
- color-interpolation-filters="sRGB"
- id="filter4588">
- <feGaussianBlur
- result="result1"
- stdDeviation="0.01"
- id="feGaussianBlur4590" />
- <feBlend
- in2="result1"
- mode="multiply"
- result="fbSourceGraphic"
- id="feBlend4592" />
- <feTurbulence
- result="result3"
- numOctaves="3"
- seed="0"
- type="fractalNoise"
- baseFrequency="0.8"
- id="feTurbulence4594" />
- <feDisplacementMap
- in2="result3"
- scale="50"
- xChannelSelector="R"
- yChannelSelector="G"
- in="fbSourceGraphic"
- result="result2"
- id="feDisplacementMap4596" />
- <feMorphology
- result="result4"
- operator="dilate"
- radius="1"
- id="feMorphology4598" />
- <feBlend
- in2="result2"
- mode="screen"
- id="feBlend4600" />
- </filter>
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4640-1"
- is_visible="true"
- pattern="M 0,0 1,0"
- copytype="single_stretched"
- prop_scale="1"
- scale_y_rel="false"
- spacing="0"
- normal_offset="0"
- tang_offset="0"
- prop_units="false"
- vertical_pattern="false"
- fuse_tolerance="0" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4644-8"
- is_visible="true"
- pattern="M 0,0 1,0"
- copytype="single_stretched"
- prop_scale="1"
- scale_y_rel="false"
- spacing="0"
- normal_offset="0"
- tang_offset="0"
- prop_units="false"
- vertical_pattern="false"
- fuse_tolerance="0" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4640-1-0"
- is_visible="true"
- pattern="M 0,0 1,0"
- copytype="single_stretched"
- prop_scale="1"
- scale_y_rel="false"
- spacing="0"
- normal_offset="0"
- tang_offset="0"
- prop_units="false"
- vertical_pattern="false"
- fuse_tolerance="0" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4644-8-3"
- is_visible="true"
- pattern="M 0,0 1,0"
- copytype="single_stretched"
- prop_scale="1"
- scale_y_rel="false"
- spacing="0"
- normal_offset="0"
- tang_offset="0"
- prop_units="false"
- vertical_pattern="false"
- fuse_tolerance="0" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4640-0"
- is_visible="true"
- pattern="M 0,0 1,0"
- copytype="single_stretched"
- prop_scale="1"
- scale_y_rel="false"
- spacing="0"
- normal_offset="0"
- tang_offset="0"
- prop_units="false"
- vertical_pattern="false"
- fuse_tolerance="0" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4644-4"
- is_visible="true"
- pattern="M 0,0 1,0"
- copytype="single_stretched"
- prop_scale="1"
- scale_y_rel="false"
- spacing="0"
- normal_offset="0"
- tang_offset="0"
- prop_units="false"
- vertical_pattern="false"
- fuse_tolerance="0" />
- <filter
- x="-0.5"
- y="-0.5"
- width="2"
- height="2"
- color-interpolation-filters="sRGB"
- id="filter4789">
- <feGaussianBlur
- result="result1"
- stdDeviation="0.01"
- id="feGaussianBlur4791" />
- <feBlend
- in2="result1"
- mode="multiply"
- result="fbSourceGraphic"
- id="feBlend4793" />
- <feTurbulence
- result="result3"
- numOctaves="3"
- seed="0"
- type="fractalNoise"
- baseFrequency="0.8"
- id="feTurbulence4795" />
- <feDisplacementMap
- in2="result3"
- scale="50"
- xChannelSelector="R"
- yChannelSelector="G"
- in="fbSourceGraphic"
- result="result2"
- id="feDisplacementMap4797" />
- <feMorphology
- result="result4"
- operator="dilate"
- radius="1"
- id="feMorphology4799" />
- <feBlend
- in2="result2"
- mode="screen"
- id="feBlend4801" />
- </filter>
- <filter
- x="-0.5"
- y="-0.5"
- width="2"
- height="2"
- color-interpolation-filters="sRGB"
- id="filter4805">
- <feGaussianBlur
- result="result1"
- stdDeviation="0.01"
- id="feGaussianBlur4807" />
- <feBlend
- in2="result1"
- mode="multiply"
- result="fbSourceGraphic"
- id="feBlend4809" />
- <feTurbulence
- result="result3"
- numOctaves="3"
- seed="0"
- type="fractalNoise"
- baseFrequency="0.8"
- id="feTurbulence4811" />
- <feDisplacementMap
- in2="result3"
- scale="50"
- xChannelSelector="R"
- yChannelSelector="G"
- in="fbSourceGraphic"
- result="result2"
- id="feDisplacementMap4813" />
- <feMorphology
- result="result4"
- operator="dilate"
- radius="1"
- id="feMorphology4815" />
- <feBlend
- in2="result2"
- mode="screen"
- id="feBlend4817" />
- </filter>
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4624-0"
- is_visible="true"
- pattern="M 0,0 1,0"
- copytype="single_stretched"
- prop_scale="1"
- scale_y_rel="false"
- spacing="0"
- normal_offset="0"
- tang_offset="0"
- prop_units="false"
- vertical_pattern="false"
- fuse_tolerance="0" />
- </defs>
- <metadata
- id="metadata3017">
- <rdf:RDF>
- <cc:Work
- rdf:about="">
- <dc:format>image/svg+xml</dc:format>
- <dc:type
- rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
- <dc:title></dc:title>
- </cc:Work>
- </rdf:RDF>
- </metadata>
- <g
- transform="translate(0,-990.36218)"
- id="layer1">
- <g
- transform="matrix(1.1985023,0,0,1.1294964,-9.8781569,-132.26612)"
- id="g3160">
- <path
- d="m 16.970563,1001.804 -0.353554,41.3658 35.708893,-0.3536 0,-32.8804 -10.253049,-8.4853 z"
- id="path3130"
- style="fill:#ffe680;stroke:#ff6600;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- inkscape:connector-curvature="0" />
- <path
- d="m 41.896077,11.441865 0,7.778175 10.076271,0"
- transform="translate(0,990.36218)"
- id="path3158"
- style="fill:none;stroke:#ff6600;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- inkscape:connector-curvature="0" />
- </g>
- <text
- x="14.200852"
- y="1020.7217"
- id="text3302"
- xml:space="preserve"
- style="font-size:9.41087437px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
- sodipodi:linespacing="125%"><tspan
- x="14.200852"
- y="1020.7217"
- id="tspan3304"
- style="font-weight:bold;-inkscape-font-specification:Sans Bold">Source </tspan><tspan
- x="14.200852"
- y="1032.4852"
- id="tspan3306"
- style="font-weight:bold;-inkscape-font-specification:Sans Bold"> Code</tspan></text>
- <g
- transform="translate(21.5,-0.5)"
- id="g4324">
- <rect
- width="75.338638"
- height="44.99205"
- x="70.080681"
- y="998.74121"
- id="rect4094-3"
- style="fill:#bec8b7;fill-opacity:1;stroke:#000000;stroke-width:1.06710124;stroke-opacity:1" />
- <path
- d="m 142.25,1020.6122 6.25,-6.75 0.25,13.5 z"
- id="path4304-5"
- style="fill:#8dd35f;fill-opacity:1;stroke:#447821;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- inkscape:connector-curvature="0" />
- <path
- d="M 73.75,30.25 67.5,23.5 67.25,37 z"
- transform="translate(0,990.36218)"
- id="path4304"
- style="fill:#8dd35f;fill-opacity:1;stroke:#447821;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- inkscape:connector-curvature="0" />
- <rect
- width="61.596703"
- height="34.279705"
- x="77.563026"
- y="1004.4252"
- transform="matrix(1.1034631,0,0,1.1194116,-11.731155,-122.4867)"
- id="rect4094"
- style="fill:#8dd35f;fill-opacity:1;stroke:#5aa02c;stroke-width:0.84222108;stroke-opacity:1" />
- <path
- d="m 62.25,-21.5 c 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 z"
- transform="translate(-18,990.36218)"
- id="path4622"
- style="fill:#000000;fill-rule:evenodd;stroke:none"
- inkscape:connector-curvature="0" />
- </g>
- <text
- x="105.21129"
- y="1024.4061"
- id="text3302-7"
- xml:space="preserve"
- style="font-size:9.41087437px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
- sodipodi:linespacing="125%"><tspan
- x="105.21129"
- y="1024.4061"
- id="tspan3306-3"
- style="font-weight:bold;-inkscape-font-specification:Sans Bold">Compiler</tspan></text>
- <g
- transform="translate(202.5,0)"
- id="g4680">
- <g
- transform="translate(16,0)"
- id="g4369">
- <path
- d="m 235,55.625 a 26.125,1.625 0 1 1 -52.25,0 26.125,1.625 0 1 1 52.25,0 z"
- transform="translate(-2,988.36218)"
- id="path4365"
- style="fill:#666666;fill-opacity:1;stroke:#000000;stroke-opacity:1"
- inkscape:connector-curvature="0" />
- <rect
- width="8.25"
- height="6"
- x="202.75"
- y="47.75"
- transform="translate(0,990.36218)"
- id="rect4361"
- style="fill:#666666;fill-opacity:1;stroke:#000000;stroke-opacity:1" />
- <rect
- width="22.5"
- height="6.5"
- x="196"
- y="43.75"
- transform="translate(0,990.36218)"
- id="rect4357"
- style="fill:#666666;fill-opacity:1;stroke:#000000;stroke-opacity:1" />
- <rect
- width="48.5"
- height="40.5"
- x="182.5"
- y="997.86218"
- id="rect4353"
- style="fill:#cccccc;fill-opacity:1;stroke:#000000;stroke-opacity:1" />
- <rect
- width="43.75"
- height="35"
- x="185"
- y="1000.8622"
- id="rect4355"
- style="fill:#f9f9f9;fill-opacity:1;stroke:#808080;stroke-opacity:1" />
- </g>
- <text
- x="204.21129"
- y="1021.1561"
- id="text3302-0"
- xml:space="preserve"
- style="font-size:9.41087437px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
- sodipodi:linespacing="125%"><tspan
- x="204.21129"
- y="1021.1561"
- id="tspan3306-4"
- style="font-weight:bold;-inkscape-font-specification:Sans Bold">Output</tspan></text>
- </g>
- <g
- transform="translate(-21.938736,56.186137)"
- id="g4646">
- <path
- d="m 106.05774,963.66826 -7.911185,-4.74085 0.330852,9.99452 z"
- id="path4638"
- style="fill:#000000;fill-rule:evenodd;stroke:none"
- inkscape:connector-curvature="0" />
- <path
- d="m 101.30207,963.57555 -22.104866,-4.52079 0.217272,9.99764 z"
- id="path4642"
- style="fill:#000000;fill-rule:evenodd;stroke:none"
- inkscape:connector-curvature="0" />
- </g>
- <g
- transform="translate(96.43379,56.058417)"
- id="g4646-3">
- <path
- d="m 106.05774,963.66826 -7.911185,-4.74085 0.330852,9.99452 z"
- id="path4638-0"
- style="fill:#000000;fill-rule:evenodd;stroke:none"
- inkscape:connector-curvature="0" />
- <path
- d="m 101.30207,963.57555 -22.104866,-4.52079 0.217272,9.99764 z"
- id="path4642-5"
- style="fill:#000000;fill-rule:evenodd;stroke:none"
- inkscape:connector-curvature="0" />
- </g>
- <g
- transform="matrix(1.1985023,0,0,1.1294964,186.15244,-133.21393)"
- id="g3160-1"
- style="fill:#00ccff;fill-opacity:1;stroke:#0066ff">
- <path
- d="m 16.970563,1001.804 -0.353554,41.3658 35.708893,-0.3536 0,-32.8804 -10.253049,-8.4853 z"
- id="path3130-8"
- style="fill:#00ccff;fill-opacity:1;stroke:#0066ff;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- inkscape:connector-curvature="0" />
- <path
- d="m 41.896077,11.441865 0,7.778175 10.076271,0"
- transform="translate(0,990.36218)"
- id="path3158-3"
- style="fill:#00ccff;fill-opacity:1;stroke:#0066ff;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- inkscape:connector-curvature="0" />
- </g>
- <text
- x="210.95503"
- y="1020.4315"
- id="text3302-7-6"
- xml:space="preserve"
- style="font-size:9.41087437px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
- sodipodi:linespacing="125%"><tspan
- x="210.95503"
- y="1020.4315"
- id="tspan3306-3-1"
- style="font-weight:bold;-inkscape-font-specification:Sans Bold">Object</tspan><tspan
- x="210.95503"
- y="1032.1951"
- id="tspan4840"
- style="font-weight:bold;-inkscape-font-specification:Sans Bold"> Code</tspan></text>
- <g
- transform="translate(215.04246,-0.16425693)"
- id="g4324-8">
- <rect
- width="75.338638"
- height="44.99205"
- x="70.080681"
- y="998.74121"
- id="rect4094-3-9"
- style="fill:#ffaacc;fill-opacity:1;stroke:#000000;stroke-width:1.06710124;stroke-opacity:1" />
- <path
- d="m 142.25,1020.6122 6.25,-6.75 0.25,13.5 z"
- id="path4304-5-7"
- style="fill:#d35f8d;fill-opacity:1;stroke:#a02c5a;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- inkscape:connector-curvature="0" />
- <path
- d="M 73.75,30.25 67.5,23.5 67.25,37 z"
- transform="translate(0,990.36218)"
- id="path4304-3"
- style="fill:#d35f8d;fill-opacity:1;stroke:#a02c5a;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- inkscape:connector-curvature="0" />
- <rect
- width="61.596703"
- height="34.279705"
- x="77.563026"
- y="1004.4252"
- transform="matrix(1.1034631,0,0,1.1194116,-11.731155,-122.4867)"
- id="rect4094-2"
- style="fill:#ff80b2;fill-opacity:1;stroke:#ff0066;stroke-width:0.84222108;stroke-opacity:1" />
- <path
- d="m 62.25,-21.5 c 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 z"
- transform="translate(-18,990.36218)"
- id="path4622-3"
- style="fill:#000000;fill-rule:evenodd;stroke:none"
- inkscape:connector-curvature="0" />
- </g>
- <text
- x="300.75375"
- y="1024.7418"
- id="text3302-7-8"
- xml:space="preserve"
- style="font-size:9.41087437px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
- sodipodi:linespacing="125%"><tspan
- x="300.75375"
- y="1024.7418"
- id="tspan3306-3-0"
- style="font-weight:bold;-inkscape-font-specification:Sans Bold">Executor</tspan></text>
- <g
- transform="translate(290.5193,56.229418)"
- id="g4646-3-4">
- <path
- inkscape:connector-curvature="0"
- d="m 106.05774,963.66826 -7.911185,-4.74085 0.330852,9.99452 z"
- id="path4638-0-6"
- style="fill:#000000;fill-rule:evenodd;stroke:none" />
- <path
- inkscape:connector-curvature="0"
- d="m 101.30207,963.57555 -22.104866,-4.52079 0.217272,9.99764 z"
- id="path4642-5-2"
- style="fill:#000000;fill-rule:evenodd;stroke:none" />
- </g>
- <g
- transform="translate(173.76196,56.669731)"
- id="g4646-3-5">
- <path
- d="m 106.05774,963.66826 -7.911185,-4.74085 0.330852,9.99452 z"
- id="path4638-0-1"
- style="fill:#000000;fill-rule:evenodd;stroke:none"
- inkscape:connector-curvature="0" />
- <path
- d="m 101.30207,963.57555 -22.104866,-4.52079 0.217272,9.99764 z"
- id="path4642-5-7"
- style="fill:#000000;fill-rule:evenodd;stroke:none"
- inkscape:connector-curvature="0" />
- </g>
- </g>
-</svg>
diff --git a/_sources/GeneralIntro/Figures/interpret.png b/_sources/GeneralIntro/Figures/interpret.png
deleted file mode 100644
index f8a631f3..00000000
Binary files a/_sources/GeneralIntro/Figures/interpret.png and /dev/null differ
diff --git a/_sources/GeneralIntro/Figures/interpret.svg b/_sources/GeneralIntro/Figures/interpret.svg
deleted file mode 100644
index cbf64107..00000000
--- a/_sources/GeneralIntro/Figures/interpret.svg
+++ /dev/null
@@ -1,445 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-
-<svg
- xmlns:dc="http://purl.org/dc/elements/1.1/"
- xmlns:cc="http://creativecommons.org/ns#"
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
- version="1.1"
- width="264"
- height="62"
- id="svg3012">
- <defs
- id="defs3014">
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4644" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4640" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4636" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4632" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4628" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4624" />
- <inkscape:path-effect
- effect="spiro"
- id="path-effect3148" />
- <inkscape:path-effect
- effect="spiro"
- id="path-effect3136" />
- <filter
- x="-0.5"
- y="-0.5"
- width="2"
- height="2"
- color-interpolation-filters="sRGB"
- id="filter3288">
- <feGaussianBlur
- id="feGaussianBlur3290"
- stdDeviation="0.01"
- result="result1" />
- <feBlend
- in2="result1"
- mode="multiply"
- result="fbSourceGraphic"
- id="feBlend3292" />
- <feTurbulence
- id="feTurbulence3294"
- baseFrequency="0.8"
- type="fractalNoise"
- seed="0"
- numOctaves="3"
- result="result3" />
- <feDisplacementMap
- in2="result3"
- scale="50"
- xChannelSelector="R"
- yChannelSelector="G"
- in="fbSourceGraphic"
- result="result2"
- id="feDisplacementMap3296" />
- <feMorphology
- id="feMorphology3298"
- radius="1"
- operator="dilate"
- result="result4" />
- <feBlend
- in2="result2"
- mode="screen"
- id="feBlend3300" />
- </filter>
- <filter
- color-interpolation-filters="sRGB"
- id="filter4280">
- <feGaussianBlur
- id="feGaussianBlur4282"
- result="result1"
- stdDeviation="3" />
- <feBlend
- in2="result1"
- mode="multiply"
- in="result1"
- result="result5"
- id="feBlend4284" />
- <feGaussianBlur
- id="feGaussianBlur4286"
- in="result5"
- result="result6"
- stdDeviation="1" />
- <feComposite
- in2="result5"
- operator="xor"
- in="result6"
- result="result8"
- id="feComposite4288" />
- <feComposite
- in2="result8"
- operator="xor"
- in="result6"
- result="fbSourceGraphic"
- id="feComposite4290" />
- <feSpecularLighting
- id="feSpecularLighting4292"
- in="fbSourceGraphic"
- result="result1"
- lighting-color="#ffffff"
- surfaceScale="2"
- specularConstant="2.20000005"
- specularExponent="55">
- <fePointLight
- id="fePointLight4294"
- x="-5000"
- y="-10000"
- z="20000" />
- </feSpecularLighting>
- <feComposite
- in2="fbSourceGraphic"
- operator="in"
- in="result1"
- result="result2"
- id="feComposite4296" />
- <feComposite
- in2="result2"
- operator="arithmetic"
- k1="0"
- k2="2"
- k3="1"
- k4="0"
- in="fbSourceGraphic"
- result="result4"
- id="feComposite4298" />
- <feComposite
- in2="result4"
- operator="in"
- result="result91"
- id="feComposite4300" />
- <feBlend
- in2="result91"
- mode="darken"
- id="feBlend4302" />
- </filter>
- <filter
- color-interpolation-filters="sRGB"
- id="filter4329">
- <feGaussianBlur
- id="feGaussianBlur4331"
- result="result1"
- stdDeviation="3" />
- <feBlend
- in2="result1"
- mode="multiply"
- in="result1"
- result="result5"
- id="feBlend4333" />
- <feGaussianBlur
- id="feGaussianBlur4335"
- in="result5"
- result="result6"
- stdDeviation="1" />
- <feComposite
- in2="result5"
- operator="xor"
- in="result6"
- result="result8"
- id="feComposite4337" />
- <feComposite
- in2="result8"
- operator="xor"
- in="result6"
- result="fbSourceGraphic"
- id="feComposite4339" />
- <feSpecularLighting
- id="feSpecularLighting4341"
- in="fbSourceGraphic"
- result="result1"
- lighting-color="#ffffff"
- surfaceScale="2"
- specularConstant="2.20000005"
- specularExponent="55">
- <fePointLight
- id="fePointLight4343"
- x="-5000"
- y="-10000"
- z="20000" />
- </feSpecularLighting>
- <feComposite
- in2="fbSourceGraphic"
- operator="in"
- in="result1"
- result="result2"
- id="feComposite4345" />
- <feComposite
- in2="result2"
- operator="arithmetic"
- k1="0"
- k2="2"
- k3="1"
- k4="0"
- in="fbSourceGraphic"
- result="result4"
- id="feComposite4347" />
- <feComposite
- in2="result4"
- operator="in"
- result="result91"
- id="feComposite4349" />
- <feBlend
- in2="result91"
- mode="darken"
- id="feBlend4351" />
- </filter>
- <filter
- x="-0.5"
- y="-0.5"
- width="2"
- height="2"
- color-interpolation-filters="sRGB"
- id="filter4588">
- <feGaussianBlur
- id="feGaussianBlur4590"
- stdDeviation="0.01"
- result="result1" />
- <feBlend
- in2="result1"
- mode="multiply"
- result="fbSourceGraphic"
- id="feBlend4592" />
- <feTurbulence
- id="feTurbulence4594"
- baseFrequency="0.8"
- type="fractalNoise"
- seed="0"
- numOctaves="3"
- result="result3" />
- <feDisplacementMap
- in2="result3"
- scale="50"
- xChannelSelector="R"
- yChannelSelector="G"
- in="fbSourceGraphic"
- result="result2"
- id="feDisplacementMap4596" />
- <feMorphology
- id="feMorphology4598"
- radius="1"
- operator="dilate"
- result="result4" />
- <feBlend
- in2="result2"
- mode="screen"
- id="feBlend4600" />
- </filter>
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4640-1" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4644-8" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4640-1-0" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4644-8-3" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4640-0" />
- <inkscape:path-effect
- effect="skeletal"
- id="path-effect4644-4" />
- </defs>
- <metadata
- id="metadata3017">
- <rdf:RDF>
- <cc:Work
- rdf:about="">
- <dc:format>image/svg+xml</dc:format>
- <dc:type
- rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
- <dc:title></dc:title>
- </cc:Work>
- </rdf:RDF>
- </metadata>
- <g
- transform="translate(0,-990.36218)"
- id="layer1">
- <g
- transform="matrix(1.2068615,0,0,1.0550748,-9.4956719,-57.395647)"
- id="g3160">
- <path
- d="m 16.970563,1001.804 -0.353554,41.3658 35.708893,-0.3536 0,-32.8804 -10.253049,-8.4853 z"
- id="path3130"
- style="fill:#ffe680;stroke:#ff6600;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1" />
- <path
- d="m 41.896077,11.441865 0,7.778175 10.076271,0"
- transform="translate(0,990.36218)"
- id="path3158"
- style="fill:none;stroke:#ff6600;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1" />
- </g>
- <text
- x="14.200852"
- y="1020.7217"
- id="text3302"
- xml:space="preserve"
- style="font-size:9.41087437px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"><tspan
- x="14.200852"
- y="1020.7217"
- id="tspan3304"
- style="font-weight:bold;-inkscape-font-specification:Sans Bold">Source </tspan><tspan
- x="14.200852"
- y="1032.4852"
- id="tspan3306"
- style="font-weight:bold;-inkscape-font-specification:Sans Bold"> Code</tspan></text>
- <g
- transform="translate(23.5,-0.5)"
- id="g4324">
- <rect
- width="75.338638"
- height="44.99205"
- x="70.080681"
- y="998.74121"
- id="rect4094-3"
- style="fill:#bec8b7;fill-opacity:1;stroke:#000000;stroke-width:1.06710124;stroke-opacity:1" />
- <path
- d="m 142.25,1020.6122 6.25,-6.75 0.25,13.5 z"
- id="path4304-5"
- style="fill:#8dd35f;fill-opacity:1;stroke:#447821;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1" />
- <path
- d="M 73.75,30.25 67.5,23.5 67.25,37 z"
- transform="translate(0,990.36218)"
- id="path4304"
- style="fill:#8dd35f;fill-opacity:1;stroke:#447821;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1" />
- <rect
- width="61.596703"
- height="34.279705"
- x="77.563026"
- y="1004.4252"
- transform="matrix(1.1034631,0,0,1.1194116,-11.731155,-122.4867)"
- id="rect4094"
- style="fill:#8dd35f;fill-opacity:1;stroke:#5aa02c;stroke-width:0.84222108;stroke-opacity:1" />
- <path
- d="m 62.25,-21.5 c 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 0,0 z"
- transform="translate(-18,990.36218)"
- id="path4622"
- style="fill:#000000;fill-rule:evenodd;stroke:none" />
- </g>
- <text
- x="101.21129"
- y="1024.4061"
- id="text3302-7"
- xml:space="preserve"
- style="font-size:9.41087437px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"><tspan
- x="101.21129"
- y="1024.4061"
- id="tspan3306-3"
- style="font-weight:bold;-inkscape-font-specification:Sans Bold">Interpreter</tspan></text>
- <g
- transform="translate(6.5,0)"
- id="g4680">
- <g
- transform="translate(16,0)"
- id="g4369">
- <path
- d="m 235,55.625 a 26.125,1.625 0 1 1 -52.25,0 26.125,1.625 0 1 1 52.25,0 z"
- transform="translate(-2,988.36218)"
- id="path4365"
- style="fill:#666666;fill-opacity:1;stroke:#000000;stroke-opacity:1" />
- <rect
- width="8.25"
- height="6"
- x="202.75"
- y="47.75"
- transform="translate(0,990.36218)"
- id="rect4361"
- style="fill:#666666;fill-opacity:1;stroke:#000000;stroke-opacity:1" />
- <rect
- width="22.5"
- height="6.5"
- x="196"
- y="43.75"
- transform="translate(0,990.36218)"
- id="rect4357"
- style="fill:#666666;fill-opacity:1;stroke:#000000;stroke-opacity:1" />
- <rect
- width="48.5"
- height="40.5"
- x="182.5"
- y="997.86218"
- id="rect4353"
- style="fill:#cccccc;fill-opacity:1;stroke:#000000;stroke-opacity:1" />
- <rect
- width="43.75"
- height="35"
- x="185"
- y="1000.8622"
- id="rect4355"
- style="fill:#f9f9f9;fill-opacity:1;stroke:#808080;stroke-opacity:1" />
- </g>
- <text
- x="204.21129"
- y="1021.1561"
- id="text3302-0"
- xml:space="preserve"
- style="font-size:9.41087437px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"><tspan
- x="204.21129"
- y="1021.1561"
- id="tspan3306-4"
- style="font-weight:bold;-inkscape-font-specification:Sans Bold">Output</tspan></text>
- </g>
- <g
- transform="translate(-17.938736,56.186137)"
- id="g4646">
- <path
- d="m 106.05774,963.66826 -7.911185,-4.74085 0.330852,9.99452 z"
- id="path4638"
- style="fill:#000000;fill-rule:evenodd;stroke:none" />
- <path
- d="m 101.30207,963.57555 -22.104866,-4.52079 0.217272,9.99764 z"
- id="path4642"
- style="fill:#000000;fill-rule:evenodd;stroke:none" />
- </g>
- <g
- transform="translate(96.43379,56.058417)"
- id="g4646-3">
- <path
- d="m 106.05774,963.66826 -7.911185,-4.74085 0.330852,9.99452 z"
- id="path4638-0"
- style="fill:#000000;fill-rule:evenodd;stroke:none" />
- <path
- d="m 101.30207,963.57555 -22.104866,-4.52079 0.217272,9.99764 z"
- id="path4642-5"
- style="fill:#000000;fill-rule:evenodd;stroke:none" />
- </g>
- </g>
-</svg>
diff --git a/_sources/GeneralIntro/FormalandNaturalLanguages.rst b/_sources/GeneralIntro/FormalandNaturalLanguages.rst
deleted file mode 100644
index 5cbb39f4..00000000
--- a/_sources/GeneralIntro/FormalandNaturalLanguages.rst
+++ /dev/null
@@ -1,139 +0,0 @@
-.. Copyright (C) Brad Miller, David Ranum, Jeffrey Elkner, Peter Wentworth, Allen B. Downey, Chris
- Meyers, and Dario Mitchell. Permission is granted to copy, distribute
- and/or modify this document under the terms of the GNU Free Documentation
- License, Version 1.3 or any later version published by the Free Software
- Foundation; with Invariant Sections being Forward, Prefaces, and
- Contributor List, no Front-Cover Texts, and no Back-Cover Texts. A copy of
- the license is included in the section entitled "GNU Free Documentation
- License".
-
-.. qnum::
- :prefix: intro-6-
- :start: 1
-
-Formal and Natural Languages
-----------------------------
-
-**Natural languages** are the languages that people speak, such as English,
-Spanish, Korean, and Mandarin Chinese. They were not designed by people (although people try to
-impose some order on them); they evolved naturally.
-
-**Formal languages** are languages that are designed by people for specific
-applications. For example, the notation that mathematicians use is a formal
-language that is particularly good at denoting relationships among numbers and
-symbols. Chemists use a formal language to represent the chemical structure of
-molecules. And most importantly:
-
- *Programming languages are formal languages that have been designed to
- express computations.*
-
-Formal languages tend to have strict rules about syntax. For example, ``3+3=6``
-is a syntactically correct mathematical statement, but ``3=+6$`` is not.
-H\ :sub:`2`\ O is a syntactically correct chemical name, but :sub:`2`\ Zz is
-not.
-
-Syntax rules come in two flavors, pertaining to **tokens** and structure.
-Tokens are the basic elements of the language, such as words, numbers, and
-chemical elements. One of the problems with ``3=+6$`` is that ``$`` is not a
-legal token in mathematics (at least as far as we know). Similarly,
-:sub:`2`\ Zz is not legal because there is no element with the abbreviation
-``Zz``.
-
-The second type of syntax rule pertains to the **structure** of a statement---
-that is, the way the tokens are arranged. The statement ``3=+6$`` is
-structurally illegal because you can't place a plus sign immediately after an
-equal sign. Similarly, molecular formulas have to have subscripts after the
-element name, not before.
-
-When you read a sentence in English or a statement in a formal language, you
-have to figure out what the structure of the sentence is (although in a natural
-language you do this subconsciously). This process is called **parsing**.
-
-For example, when you hear the sentence, "The other shoe fell", you understand
-that the other shoe is the subject and fell is the verb. Once you have parsed
-a sentence, you can figure out what it means, or the **semantics** of the sentence.
-Assuming that you know what a shoe is and what it means to fall, you will
-understand the general implication of this sentence.
-
-Although formal and natural languages have many features in common --- tokens,
-structure, syntax, and semantics --- there are many differences:
-
-.. glossary::
-
- ambiguity
- Natural languages are full of ambiguity, which people deal with by
- using contextual clues and other information. Formal languages are
- designed to be nearly or completely unambiguous, which means that any
- statement has exactly one meaning, regardless of context.
-
- redundancy
- In order to make up for ambiguity and reduce misunderstandings, natural
- languages employ lots of redundancy. As a result, they are often
- verbose. Formal languages are less redundant and more concise.
-
- literalness
- Formal languages mean exactly what they say. On the other hand,
- natural languages are full of idiom and metaphor. If someone says, "The
- other shoe fell", there is probably no shoe and nothing falling.
-
- .. tip::
-
- You'll need to find the original joke to understand the idiomatic
- meaning of the other shoe falling. *Yahoo! Answers* thinks it
- knows!
-
-People who grow up speaking a natural language---everyone---often have a hard
-time adjusting to formal languages. In some ways, the difference between formal
-and natural language is like the difference between poetry and prose, but more
-so:
-
-.. glossary::
-
- poetry
- Words are used for their sounds as well as for their meaning, and the
- whole poem together creates an effect or emotional response. Ambiguity
- is not only common but often deliberate.
-
- prose
- The literal meaning of words is more important, and the structure
- contributes more meaning. Prose is more amenable to analysis than
- poetry but still often ambiguous.
-
- program
- The meaning of a computer program is unambiguous and literal, and can
- be understood entirely by analysis of the tokens and structure.
-
-Here are some suggestions for reading programs (and other formal languages).
-First, remember that formal languages are much more dense than natural
-languages, so it takes longer to read them. Also, the structure is very
-important, so it is usually not a good idea to read from top to bottom, left to
-right. Instead, learn to parse the program in your head, identifying the tokens
-and interpreting the structure. Finally, the details matter. Little things
-like spelling errors and bad punctuation, which you can get away with in
-natural languages, can make a big difference in a formal language.
-
-**Check your understanding**
-
-.. mchoice:: question1_6_1
- :answer_a: natural languages can be parsed while formal languages cannot.
- :answer_b: ambiguity, redundancy, and literalness.
- :answer_c: there are no differences between natural and formal languages.
- :answer_d: tokens, structure, syntax, and semantics.
- :correct: b
- :feedback_a: Actually both languages can be parsed (determining the structure of the sentence), but formal languages can be parsed more easily in software.
- :feedback_b: All of these can be present in natural languages, but cannot exist in formal languages.
- :feedback_c: There are several differences between the two but they are also similar.
- :feedback_d: These are the similarities between the two.
-
- The differences between natural and formal languages include:
-
-.. mchoice:: question1_6_2
- :answer_a: True
- :answer_b: False
- :correct: b
- :feedback_a: It usually takes longer to read a program because the structure is as important as the content and must be interpreted in smaller pieces for understanding.
- :feedback_b: It usually takes longer to read a program because the structure is as important as the content and must be interpreted in smaller pieces for understanding.
-
- True or False: Reading a program is like reading other kinds of text.
-
-
diff --git a/_sources/GeneralIntro/Glossary.rst b/_sources/GeneralIntro/Glossary.rst
deleted file mode 100644
index b4d0043c..00000000
--- a/_sources/GeneralIntro/Glossary.rst
+++ /dev/null
@@ -1,134 +0,0 @@
-.. Copyright (C) Brad Miller, David Ranum, Jeffrey Elkner, Peter Wentworth, Allen B. Downey, Chris
- Meyers, and Dario Mitchell. Permission is granted to copy, distribute
- and/or modify this document under the terms of the GNU Free Documentation
- License, Version 1.3 or any later version published by the Free Software
- Foundation; with Invariant Sections being Forward, Prefaces, and
- Contributor List, no Front-Cover Texts, and no Back-Cover Texts. A copy of
- the license is included in the section entitled "GNU Free Documentation
- License".
-
-.. qnum::
- :prefix: intro-14-
- :start: 1
-
-Glossary
---------
-
-.. glossary::
-
- activecode
- A unique interpreter environment that allows Python to be executed from within a web browser.
-
- algorithm
- A general step by step process for solving a problem.
-
- bug
- An error in a program.
-
- byte code
- An intermediate language between source code and object code. Many
- modern languages first compile source code into byte code and then
- interpret the byte code with a program called a *virtual machine*.
-
- codelens
- An interactive environment that allows the user to control the step by step execution of a Python program
-
- comment
- Information in a program that is meant for other programmers (or anyone
- reading the source code) and has no effect on the execution of the
- program.
-
- compile
- To translate a program written in a high-level language into a
- low-level language all at once, in preparation for later execution.
-
- debugging
- The process of finding and removing any of the three kinds of
- programming errors.
-
- exception
- Another name for a runtime error.
-
- executable
- Another name for object code that is ready to be executed.
-
- formal language
- Any one of the languages that people have designed for specific
- purposes, such as representing mathematical ideas or computer programs;
- all programming languages are formal languages.
-
- high-level language
- A programming language like Python that is designed to be easy for
- humans to read and write.
-
- interpret
- To execute a program in a high-level language by translating it one
- line at a time.
-
- low-level language
- A programming language that is designed to be easy for a computer to
- execute; also called machine language or assembly language.
-
- natural language
- Any one of the languages that people speak that evolved naturally.
-
- object code
- The output of the compiler after it translates the program.
-
- parse
- To examine a program and analyze the syntactic structure.
-
- portability
- A property of a program that can run on more than one kind of computer.
-
- print function
- A function used in a program or script that causes the Python
- interpreter to display a value on its output device.
-
- problem solving
- The process of formulating a problem, finding a solution, and
- expressing the solution.
-
- program
- A sequence of instructions that specifies to a computer actions and
- computations to be performed.
-
- programming language
- A formal notation for representing solutions.
-
- Python shell
- An interactive user interface to the Python interpreter. The user of a
- Python shell types commands at the prompt (>>>), and presses the return
- key to send these commands immediately to the interpreter for
- processing.
-
- runtime error
- An error that does not occur until the program has started to execute
- but that prevents the program from continuing.
-
- semantic error
- An error in a program that makes it do something other than what the
- programmer intended.
-
- semantics
- The meaning of a program.
-
- shell mode
- A style of using Python where we type expressions at the command
- prompt, and the results are shown immediately. Contrast with
- **source code**, and see the entry under **Python shell**.
-
- source code
- A program, stored in a file, in a high-level language before being compiled or interpreted.
-
- syntax
- The structure of a program.
-
- syntax error
- An error in a program that makes it impossible to parse --- and
- therefore impossible to interpret.
-
- token
- One of the basic elements of the syntactic structure of a program,
- analogous to a word in a natural language.
-
diff --git a/_sources/GeneralIntro/MoreAboutPrograms.rst b/_sources/GeneralIntro/MoreAboutPrograms.rst
deleted file mode 100644
index 0c2697d4..00000000
--- a/_sources/GeneralIntro/MoreAboutPrograms.rst
+++ /dev/null
@@ -1,113 +0,0 @@
-.. Copyright (C) Brad Miller, David Ranum, Jeffrey Elkner, Peter Wentworth, Allen B. Downey, Chris
- Meyers, and Dario Mitchell. Permission is granted to copy, distribute
- and/or modify this document under the terms of the GNU Free Documentation
- License, Version 1.3 or any later version published by the Free Software
- Foundation; with Invariant Sections being Forward, Prefaces, and
- Contributor List, no Front-Cover Texts, and no Back-Cover Texts. A copy of
- the license is included in the section entitled "GNU Free Documentation
- License".
-
-.. qnum::
- :prefix: intro-5-
- :start: 1
-
-More About Programs
--------------------
-
-A **program** is a sequence of instructions that specifies how to perform a
-computation. The computation might be something as complex as rendering an html page in a web browser
-or encoding a video and streaming it across the network. It can also be a
-symbolic computation, such as searching for and replacing text in a document or
-(strangely enough) compiling a program.
-
-The details look different in different languages, but a few basic instructions
-appear in just about every language.
-
-input
- Get data from the keyboard, a file, or some other device.
-
-output
- Display data on the screen or send data to a file or other device.
-
-math and logic
- Perform basic mathematical operations like addition and multiplication
- and logical operations like ``and``, ``or``, and ``not``.
-
-conditional execution
- Check for certain conditions and execute the appropriate sequence of
- statements.
-
-repetition
- Perform some action repeatedly, usually with some variation.
-
-Believe it or not, that's pretty much all there is to it. Every program you've
-ever used, no matter how complicated, is made up of instructions that look more
-or less like these. Thus, we can describe programming as the process of
-breaking a large, complex task into smaller and smaller subtasks until the
-subtasks are simple enough to be performed with sequences of these basic
-instructions.
-
-.. That may be a little vague, but we will come back to this topic later when we
-.. talk about **algorithms**.
-
-Preview of Control Structures
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-We won't get too much into python control structures yet, but it is good to mention them early to give you a taste for what you can do with the language!
-If these make sense to you now, that's great!
-However, we don't expect you to understand these yet - understanding will come later.
-
-First we have structures that allow us to iterate over something.
-We can look at strings character-by-character or lists item-by-item until we've reached the end of them by using something called a ``for`` loop.
-
-.. activecode:: ac1_5_1
-
- for character in "Cool string":
- print(character)
-
-We can also iterate without a definite stopping point with ``while`` loops.
-You might use this if you want to receive input from the user of your program but you don't know how long it'll take for them to be done with your code.
-
-.. activecode:: ac1_5_2
-
- grocery_item = ""
- while grocery_item != "done":
- grocery_item = input("Please write down an item to add to your grocery list. When you are done writing the list then simply type: done")
- print(grocery_item)
-
-Other structures will allow us to only run parts of our programs or only do some task if a certain set of conditions are found.
-Conditionals, as they're called, allow us to do that.
-Check out how adding conditionals to our code can change what we can write about regarding grocery shopping.
-
-.. activecode:: ac1_5_3
-
- grocery_item = ""
- grocery_list = []
- while grocery_item != "done":
- grocery_item = input("Please write down an item to add to your grocery list. When you are done writing the list then simply type: done")
- if grocery_item == 'done':
- continue
- else:
- print("adding the item to the list")
- grocery_list.append(grocery_item)
- print("Here is our grocery list:")
- print(grocery_list)
-
-**Check your understanding**
-
-.. mchoice:: question1_5_1
- :answer_a: a sequence of instructions that specifies how to perform a computation.
- :answer_b: something you follow along at a play or concert.
- :answer_c: a computation, even a symbolic computation.
- :answer_d: the same thing as an algorithm.
- :correct: a
- :feedback_a: It is just step-by-step instructions that the computer can understand and execute. Programs often implement algorithms, but note that algorithms are typically less precise than programs and do not have to be written in a programming language.
- :feedback_b: True, but not in this context. We mean a program as related to a computer.
- :feedback_c: A program can perform a computation, but by itself it is not one.
- :feedback_d: Programs often implement algorithms, but they are not the same thing. An algorithm is a step by step list of instructions, but those instructions are not necessarily precise enough for a computer to follow. A program must be written in a programming language that the computer knows how to interpret.
-
- A program is:
-
-
-.. index:: formal language, natural language, parse, token
-
diff --git a/_sources/GeneralIntro/RuntimeErrors.rst b/_sources/GeneralIntro/RuntimeErrors.rst
deleted file mode 100644
index d82b27bf..00000000
--- a/_sources/GeneralIntro/RuntimeErrors.rst
+++ /dev/null
@@ -1,54 +0,0 @@
-.. Copyright (C) Brad Miller, David Ranum, Jeffrey Elkner, Peter Wentworth, Allen B. Downey, Chris
- Meyers, and Dario Mitchell. Permission is granted to copy, distribute
- and/or modify this document under the terms of the GNU Free Documentation
- License, Version 1.3 or any later version published by the Free Software
- Foundation; with Invariant Sections being Forward, Prefaces, and
- Contributor List, no Front-Cover Texts, and no Back-Cover Texts. A copy of
- the license is included in the section entitled "GNU Free Documentation
- License".
-
-.. qnum::
- :prefix: intro-10-
- :start: 1
-
-.. index:: error;runtime, runtime error
-
-Runtime Errors
---------------
-
-The second type of error is a runtime error, so called because the error does
-not appear until you run the program. These errors are also called
-**exceptions** because they usually indicate that something exceptional (and
-bad) has happened.
-
-Runtime errors are rare in the simple programs you will see in the first few
-chapters, so it might be a while before you encounter one.
-
-**Check your understanding**
-
-.. mchoice:: question1_10_1
- :answer_a: Attempting to divide by 0.
- :answer_b: Forgetting a colon at the end of a statement where one is required.
- :answer_c: Forgetting to divide by 100 when printing a percentage amount.
- :correct: a
- :feedback_a: Python cannot reliably tell if you are trying to divide by 0 until it is executing your program (e.g., you might be asking the user for a value and then dividing by that value—you cannot know what value the user will enter before you run the program).
- :feedback_b: This is a problem with the formal structure of the program. Python knows where colons are required and can detect when one is missing simply by looking at the code without running it.
- :feedback_c: This will produce the wrong answer, but Python will not consider it an error at all. The programmer is the one who understands that the answer produced is wrong.
-
- Which of the following is a run-time error?
-
-.. mchoice:: question1_10_2
- :answer_a: The programmer.
- :answer_b: The compiler / interpreter.
- :answer_c: The computer.
- :answer_d: The teacher / instructor.
- :correct: b
- :feedback_a: Programmers rarely find all the runtime errors, there is a computer program that will do it for us.
- :feedback_b: If an instruction is illegal to perform at that point in the execution, the interpreter will stop with a message describing the exception.
- :feedback_c: Well, sort of. But it is a special thing in the computer that does it. The stand alone computer without this additional piece can not do it.
- :feedback_d: Your teacher and instructor may be able to find most of your runtime errors, but only because they have experience looking at code and possibly writing code. With experience runtime errors are easier to find. But we also have an automated way of finding these types of errors.
-
- Who or what typically finds runtime errors?
-
-
-
diff --git a/_sources/GeneralIntro/SemanticErrors.rst b/_sources/GeneralIntro/SemanticErrors.rst
deleted file mode 100644
index f92095ce..00000000
--- a/_sources/GeneralIntro/SemanticErrors.rst
+++ /dev/null
@@ -1,58 +0,0 @@
-.. Copyright (C) Brad Miller, David Ranum, Jeffrey Elkner, Peter Wentworth, Allen B. Downey, Chris
- Meyers, and Dario Mitchell. Permission is granted to copy, distribute
- and/or modify this document under the terms of the GNU Free Documentation
- License, Version 1.3 or any later version published by the Free Software
- Foundation; with Invariant Sections being Forward, Prefaces, and
- Contributor List, no Front-Cover Texts, and no Back-Cover Texts. A copy of
- the license is included in the section entitled "GNU Free Documentation
- License".
-
-.. qnum::
- :prefix: intro-11-
- :start: 1
-
-.. index:: semantic error, logic error, error; semantic, error; logic
-
-Semantic Errors
----------------
-
-The third type of error is the **semantic error**. If there is a semantic error
-in your program, it will run successfully in the sense that the computer will
-not generate any error messages. However, your program will not do the right thing. It will do
-something else. Specifically, it will do what you told it to do.
-
-The problem is that the program you wrote is not the program you wanted to
-write. The meaning of the program (its semantics) is wrong. Identifying
-semantic errors can be tricky because it requires you to work backward by
-looking at the output of the program and trying to figure out what it is doing.
-
-**Check your understanding**
-
-.. mchoice:: question1_11_1
- :answer_a: Attempting to divide by 0.
- :answer_b: Forgetting a semi-colon at the end of a statement where one is required.
- :answer_c: Forgetting to divide by 100 when printing a percentage amount.
- :correct: c
- :feedback_a: A semantic error is an error in logic. In this case the program does not produce the correct output because the problem is not solved correctly. This would be considered a run-time error.
- :feedback_b: A semantic error is an error in logic. In this case the program does not produce the correct output because the code can not be processed by the compiler or interpreter. This would be considered a syntax error.
- :feedback_c: This will produce the wrong answer because the programmer implemented the solution incorrectly. This is a semantic error.
-
- Which of the following is a semantic error?
-
-.. mchoice:: question1_11_2
- :answer_a: The programmer.
- :answer_b: The compiler / interpreter.
- :answer_c: The computer.
- :answer_d: The teacher / instructor.
- :correct: a
- :feedback_a: You must fully understand the problem so the you can tell if your program properly solves it.
- :feedback_b: The compiler and / or interpreter will only do what you instruct it to do. It does not understand what the problem is that you want to solve.
- :feedback_c: The computer does not understand your problem. It just executes the instructions that it is given.
- :feedback_d: Your teacher and instructor may be able to find most of your semantic errors, but only because they have experience solving problems. However it is your responsibility to understand the problem so you can develop a correct solution.
-
- Who or what typically finds semantic errors?
-
-.. index::
- single: Holmes, Sherlock
- single: Doyle, Arthur Conan
- single: Linux
diff --git a/_sources/GeneralIntro/SpecialWaystoExecutePythoninthisBook.rst b/_sources/GeneralIntro/SpecialWaystoExecutePythoninthisBook.rst
deleted file mode 100644
index b0b7352a..00000000
--- a/_sources/GeneralIntro/SpecialWaystoExecutePythoninthisBook.rst
+++ /dev/null
@@ -1,118 +0,0 @@
-.. Copyright (C) Brad Miller, David Ranum, Jeffrey Elkner, Peter Wentworth, Allen B. Downey, Chris
- Meyers, and Dario Mitchell. Permission is granted to copy, distribute
- and/or modify this document under the terms of the GNU Free Documentation
- License, Version 1.3 or any later version published by the Free Software
- Foundation; with Invariant Sections being Forward, Prefaces, and
- Contributor List, no Front-Cover Texts, and no Back-Cover Texts. A copy of
- the license is included in the section entitled "GNU Free Documentation
- License".
-
-.. qnum::
- :prefix: intro-4-
- :start: 1
-
-Special Ways to Execute Python in this Book
--------------------------------------------
-
-.. video:: codelensvid
- :controls:
- :thumb: ../_static/activecodethumb.png
-
- http://media.interactivepython.org/thinkcsVideos/activecodelens.mov
- http://media.interactivepython.org/thinkcsVideos/activecodelens.webm
-
-This book provides two additional ways to execute Python programs. Both techniques are designed to assist you as you
-learn the Python programming language. They will help you increase your understanding of how Python programs work.
-
-
-First, you can write, modify, and execute programs using a unique **activecode** interpreter that allows you to execute Python code right
-in the text itself (right from the web browser). Although this is certainly not the way real programs are written, it provides an excellent
-environment for learning a programming language like Python since you can experiment with the language as you are reading.
-
-Take a look at the activecode interpreter in action. If we use the Python code from the previous example and make it active, you will see that it can be executed directly by pressing the *Save & Run* button. Try pressing the *Save & Run* button below.
-
-.. activecode:: ac1_4_1
-
- print("My first program adds two numbers, 2 and 3:")
- print(2 + 3)
-
-Now try modifying the activecode program shown above. First, modify the string in the
-first print statement by changing the word *adds* to the word *multiplies*. Now press
-*run*. You can see that the result of the program has changed. However, it still prints
-"5" as the answer. Modify the second print statement by changing the addition symbol, the
-``+``, to the multiplication symbol, ``*``. Press *Run* to see the new results.
-
-Note that if you are logged in, you should see a green *Save & Run* button. If you are not
-logged in you see only *Run*.
-
-If we use the Python code from the previous example and make it active,
-you will see that it can be executed directly by pressing the *Run* button.
-Try pressing the *Run* (or *Save & Run*) button above.
-
-As the name suggests, *Save & Run* also *saves* your latest version of the code,
-and you can recover it even in later sessions when *logged in*. If *not* logged in,
-*Run* saves versions *only until your browser leaves the current web page*,
-and then you lose all modifications.
-
-After you have run your code the first time,
-a *Load History* button that was beside the *Run* button turns into a slider.
-If you click on the slider location box, you can use your left and right arrow
-buttons to switch to other versions you ran.
-Alternately you can drag the box on the slider.
-Now move the slider to see a previously saved state. You can just run it
-by pressing *Run*, or edit and then save and run it as the latest version.
-
-In addition to activecode, you can also execute Python code with the assistance of a unique
-visualization tool. This tool, known as **codelens**, allows you to control the step by
-step execution of a program. It also lets you see the values of all variables as they are
-created and modified. In activecode, the source code executes from beginning to end and you
-can see the final result. In codelens you can see and control the step by step progress.
-Note that the red arrow always points to the next line of code that is going to be executed.
-The light green arrow points to the line that was just executed. Click on the "Show in
-Codelens" button to make the codelens window show up, and then click on the Forward button
-a few times to step through the execution.
-
-Sometimes, we will present code examples explicitly in a codelens window, as below.
-When we do, think of it as an encouragement to use the codelens features to step through the
-execution of the program.
-
-.. codelens:: clens1_4_1
- :python: py3
- :showoutput:
-
- print("My first program adds two numbers, 2 and 3:")
- print(2 + 3)
-
-
-**Check your understanding**
-
-.. mchoice:: question1_4_1
- :multiple_answers:
- :answer_a: save programs and reload saved programs.
- :answer_b: type in Python source code.
- :answer_c: execute Python code right in the text itself within the web browser.
- :answer_d: receive a yes/no answer about whether your code is correct or not.
- :correct: a,b,c
- :feedback_a: You can (and should) save the contents of the activecode window.
- :feedback_b: You are not limited to running the examples that are already there. Try adding to them and creating your own.
- :feedback_c: The activecode interpreter will allow you type Python code into the textbox and then you can see it execute as the interpreter interprets and executes the source code.
- :feedback_d: Although you can (and should) verify that your code is correct by examining its output, activecode will not directly tell you whether you have correctly implemented your program.
-
- The activecode interpreter allows you to (select all that apply):
-
-.. mchoice:: question1_4_2
- :multiple_answers:
- :answer_a: measure the speed of a program’s execution.
- :answer_b: control the step by step execution of a program.
- :answer_c: write and execute your own Python code.
- :answer_d: execute the Python code that is in codelens.
- :correct: b,d
- :feedback_a: In fact, codelens steps through each line one by one as you click, which is MUCH slower than the Python interpreter.
- :feedback_b: By using codelens, you can control the execution of a program step by step. You can even go backwards!
- :feedback_c: Codelens works only for the pre-programmed examples.
- :feedback_d: By stepping forward through the Python code in codelens, you are executing the Python program.
-
- Codelens allows you to (select all that apply):
-
-.. index:: program, algorithm
-
diff --git a/_sources/GeneralIntro/Syntaxerrors.rst b/_sources/GeneralIntro/Syntaxerrors.rst
deleted file mode 100644
index f0de267f..00000000
--- a/_sources/GeneralIntro/Syntaxerrors.rst
+++ /dev/null
@@ -1,66 +0,0 @@
-.. Copyright (C) Brad Miller, David Ranum, Jeffrey Elkner, Peter Wentworth, Allen B. Downey, Chris
- Meyers, and Dario Mitchell. Permission is granted to copy, distribute
- and/or modify this document under the terms of the GNU Free Documentation
- License, Version 1.3 or any later version published by the Free Software
- Foundation; with Invariant Sections being Forward, Prefaces, and
- Contributor List, no Front-Cover Texts, and no Back-Cover Texts. A copy of
- the license is included in the section entitled "GNU Free Documentation
- License".
-
-.. qnum::
- :prefix: intro-9-
- :start: 1
-
-.. index:: syntax error, error; syntax
-
-Syntax errors
--------------
-
-Python can only execute a program if the program is syntactically correct;
-otherwise, the process fails and returns an error message. **Syntax** refers
-to the structure of a program and the rules about that structure. For example,
-in English, a sentence must begin with a capital letter and end with a period.
-this sentence contains a **syntax error**. So does this one
-
-For most readers, a few syntax errors are not a significant problem, which is
-why we can read the poetry of e. e. cummings without problems.
-Python is not so forgiving. If there is a single syntax error anywhere in your
-program, Python will display an error message and quit. You will not be able
-to complete the execution of your program. During the first few weeks of your programming career, you
-will probably spend a lot of time tracking down syntax errors. However, as you gain
-experience, you will make fewer errors and you will also be able to find your errors faster.
-
-Can you spot the syntax error in the code below?
-
-.. activecode:: ac1_9_1
-
- print("Hello World!"
-
-**Check your understanding**
-
-.. mchoice:: question1_9_1
- :answer_a: Attempting to divide by 0.
- :answer_b: Forgetting a colon at the end of a statement where one is required.
- :answer_c: Forgetting to divide by 100 when printing a percentage amount.
- :correct: b
- :feedback_a: A syntax error is an error in the structure of the python code that can be detected before the program is executed. Python cannot usually tell if you are trying to divide by 0 until it is executing your program (e.g., you might be asking the user for a value and then dividing by that value—you cannot know what value the user will enter before you run the program).
- :feedback_b: This is a problem with the formal structure of the program. Python knows where colons are required and can detect when one is missing simply by looking at the code without running it.
- :feedback_c: This will produce the wrong answer, but Python will not consider it an error at all. The programmer is the one who understands that the answer produced is wrong.
-
- Which of the following is a syntax error?
-
-.. mchoice:: question1_9_2
- :answer_a: The programmer.
- :answer_b: The compiler / interpreter.
- :answer_c: The computer.
- :answer_d: The teacher / instructor.
- :correct: b
- :feedback_a: Programmers rarely find all the syntax errors, there is a computer program that will do it for us.
- :feedback_b: The compiler and / or interpreter is a computer program that determines if your program is written in a way that can be translated into machine language for execution.
- :feedback_c: Well, sort of. But it is a special thing in the computer that does it. The stand alone computer without this additional piece can not do it.
- :feedback_d: Your teacher and instructor may be able to find most of your syntax errors, but only because they have experience looking at code and possibly writing code. With experience syntax errors are easier to find. But we also have an automated way of finding these types of errors.
-
- Who or what typically finds syntax errors?
-
-.. index:: runtime error, exception, safe language
-
diff --git a/_sources/GeneralIntro/ThePythonProgrammingLanguage.rst b/_sources/GeneralIntro/ThePythonProgrammingLanguage.rst
deleted file mode 100644
index 5b4b526c..00000000
--- a/_sources/GeneralIntro/ThePythonProgrammingLanguage.rst
+++ /dev/null
@@ -1,174 +0,0 @@
-.. Copyright (C) Brad Miller, David Ranum, Jeffrey Elkner, Peter Wentworth, Allen B. Downey, Chris
- Meyers, and Dario Mitchell. Permission is granted to copy, distribute
- and/or modify this document under the terms of the GNU Free Documentation
- License, Version 1.3 or any later version published by the Free Software
- Foundation; with Invariant Sections being Forward, Prefaces, and
- Contributor List, no Front-Cover Texts, and no Back-Cover Texts. A copy of
- the license is included in the section entitled "GNU Free Documentation
- License".
-
-.. qnum::
- :prefix: intro-3-
- :start: 1
-
-The Python Programming Language
--------------------------------
-
-The programming language you will be learning is Python. Python is an example
-of a **high-level language**; other high-level languages you might have heard
-of are C++, PHP, and Java.
-
-As you might infer from the name high-level language, there are also
-**low-level languages**, sometimes referred to as machine languages or assembly
-languages. Loosely speaking, computers can only execute programs written in
-low-level languages. Thus, programs written in a high-level language have to be
-processed before they can run. This extra processing takes some time, which is
-a small disadvantage of high-level languages.
-However, the advantages to high-level languages are enormous.
-
-First, it is much easier to program in a
-high-level language. Programs written in a high-level language take less time
-to write, they are shorter and easier to read, and they are more likely to be
-correct. Second, high-level languages are **portable**, meaning that they can
-run on different kinds of computers with few or no modifications. Low-level
-programs can run on only one kind of computer and have to be rewritten to run
-on another.
-
-Due to these advantages, almost all programs are written in high-level
-languages. Low-level languages are used only for a few specialized
-applications.
-
-Two kinds of programs process high-level languages into low-level languages:
-**interpreters** and **compilers**. An interpreter reads a high-level program
-and executes it, meaning that it does what the program says. It processes the
-program a little at a time, alternately reading lines and performing
-computations.
-
-.. image:: Figures/interpret.png
- :alt: Interpret illustration
-
-A compiler reads the program and translates it completely before the program
-starts running. In this case, the high-level program is called the **source
-code**, and the translated program is called the **object code** or the
-**executable**. Once a program is compiled, you can execute it repeatedly
-without further translation.
-
-.. image:: Figures/compile.png
- :alt: Compile illustration
-
-Many modern languages use both processes. They are first compiled into a lower
-level language, called **byte code**, and then interpreted by a program called
-a **virtual machine**. Python uses both processes, but because of the way
-programmers interact with it, it is usually considered an interpreted language.
-
-In this book, and for the first half of this course, you will not need to install
-or run python natively on your computer. Instead, you'll be writing simple
-programs and executing them right in your browser. About midway through
-the course, you will install python, and then the next few paragraphs will
-apply. Consider them a preview for now.
-
-There are two ways to use the Python interpreter: *shell mode* and *program
-mode*. In shell mode, you type Python expressions into the **Python shell**,
-and the interpreter immediately shows the result. The example below shows the Python shell at work.
-
-::
-
- $ python3
- Python 3.5.2 (r32:88445, Mar 25 2011, 19:28:28)
- [GCC 4.5.2] on linux2
- Type "help", "copyright", "credits" or "license" for more information.
- >>> 2 + 3
- 5
- >>>
-
-The ``>>>`` is called the **Python prompt**. The interpreter uses the prompt to
-indicate that it is ready for instructions. We typed ``2 + 3``. The
-interpreter evaluated our expression and replied ``5``. On the next line
-it gave a new prompt indicating that it is ready for more input.
-
-Working directly in the interpreter is convenient for testing short bits of
-code because you get immediate feedback. Think of it as scratch paper used to
-help you work out problems.
-
-Alternatively, you can write an entire program by placing lines of Python instructions
-in a file and then use the interpreter to
-execute the contents of the file as a whole. Such a file is often referred to as **source code**. For
-example, we will use a text editor to create a source code file named ``firstprogram.py`` with
-the following contents:
-
-.. sourcecode:: python
-
- print("My first program adds two numbers, 2 and 3:")
- print(2 + 3)
-
-
-By convention, files that contain Python programs have names that end with
-``.py`` . Following this convention will help your operating system and other
-programs identify a file as containing python code.
-
-::
-
- $ python firstprogram.py
- My first program adds two numbers, 2 and 3:
- 5
-
-These examples show Python being run from a Unix command line. In other
-development environments, the details of executing programs may differ. Also,
-most programs are more interesting than this one.
-
-.. note::
-
- In this textbook, we will not make use of the interactive python shell. We have found that it is quite confusing to students because the interactive shell shows the value of expressions, which are not normally revealed during a program's execution unless the print function is invoked. This textbook reinforces the notion that there is a difference between the internal state of a program during execution, and visible outputs, which are caused by invocations of the print function.
-
-.. admonition:: Want to learn more about Python?
-
- If you would like to learn more about installing and using Python, here are some video links.
- `Installing Python for Windows <http://youtu.be/9EfGpN1Pnsg>`__ shows you how to install the Python environment under
- Windows Vista,
- `Installing Python for Mac <http://youtu.be/MEmEJCLLI2k>`__ shows you how to install under Mac OS/X, and
- `Installing Python for Linux <http://youtu.be/RLPYBxfAud4>`__ shows you how to install from the Linux
- command line.
- `Using Python <http://youtu.be/kXbpB5_ywDw>`__ shows you some details about the Python shell and source code.
-
-**Check your understanding**
-
-.. mchoice:: question1_3_1
- :answer_a: the instructions in a program, written in a high-level language.
- :answer_b: the language that you are programming in (e.g., Python).
- :answer_c: the environment/tool in which you are programming.
- :answer_d: the number (or “code”) that you must input at the top of each program to tell the computer how to execute your program.
- :correct: a
- :feedback_a: If the instructions are strored in a file, it is called the source code file.
- :feedback_b: This language is simply called the programming language, or simply the language. Programs are writte in this language.
- :feedback_c: The environment may be called the IDE, or integrated development environment, though not always.
- :feedback_d: There is no such number that you must type in at the start of your program.
-
- Source code is another name for:
-
-.. mchoice:: question1_3_2
- :answer_a: It is high-level if you are standing and low-level if you are sitting.
- :answer_b: It is high-level if you are programming for a computer and low-level if you are programming for a phone or mobile device.
- :answer_c: It is high-level if the program must be processed before it can run, and low-level if the computer can execute it without additional processing.
- :answer_d: It is high-level if it easy to program in and is very short; it is low-level if it is really hard to program in and the programs are really long.
- :correct: c
- :feedback_a: In this case high and low have nothing to do with altitude.
- :feedback_b: High and low have nothing to do with the type of device you are programming for. Instead, look at what it takes to run the program written in the language.
- :feedback_c: Python is a high level language but must be interpreted into machine code (binary) before it can be executed.
- :feedback_d: While it is true that it is generally easier to program in a high-level language and programs written in a high-level language are usually shorter, this is not always the case.
-
- What is the difference between a high-level programming language and a low-level programming language?
-
-.. mchoice:: question1_3_3
- :answer_a: 1 = a process, 2 = a function
- :answer_b: 1 = translating an entire book, 2 = translating a line at a time
- :answer_c: 1 = software, 2 = hardware
- :answer_d: 1 = object code, 2 = byte code
- :correct: b
- :feedback_a: Compiling is a software process, and running the interpreter is invoking a function, but how is a process different than a function?
- :feedback_b: Compilers take the entire source code and produce object code or the executable and interpreters execute the code line by line.
- :feedback_c: Both compilers and interpreters are software.
- :feedback_d: Compilers can produce object code or byte code depending on the language. An interpreter produces neither.
-
- Pick the best replacements for 1 and 2 in the following sentence: When comparing compilers and interpreters, a compiler is like 1 while an interpreter is like 2.
-
-
diff --git a/_sources/GeneralIntro/intro-TheWayoftheProgram.rst b/_sources/GeneralIntro/intro-TheWayoftheProgram.rst
deleted file mode 100644
index 2cb54795..00000000
--- a/_sources/GeneralIntro/intro-TheWayoftheProgram.rst
+++ /dev/null
@@ -1,46 +0,0 @@
-.. Copyright (C) Brad Miller, David Ranum, Jeffrey Elkner, Peter Wentworth, Allen B. Downey, Chris
- Meyers, and Dario Mitchell. Permission is granted to copy, distribute
- and/or modify this document under the terms of the GNU Free Documentation
- License, Version 1.3 or any later version published by the Free Software
- Foundation; with Invariant Sections being Forward, Prefaces, and
- Contributor List, no Front-Cover Texts, and no Back-Cover Texts. A copy of
- the license is included in the section entitled "GNU Free Documentation
- License".
-
-
-Introduction: The Way of the Program
-====================================
-
-The goal of this book is to teach you to understand and create computer programs in Python.
-You will use that ability to shed light on how people and computers are alike
-and different as processors of information. This book provides
-a human-centric view of computer programming.
-
-Understanding computer programs requires algorithmic, mechanistic thinking.
-Programs specify mechanistic sequences of actions to perform; when executed,
-they transform input data into output data. They execute very reliably, and
-very fast, but not creatively. Computers do what you tell them to do, not you
-mean for them to do. Understanding computer code, and especially debugging it,
-involves a lot of mental simulation of what will actually happen, not what you
-wish would happen. This way of thinking combines some of the best features of
-mathematics, engineering, and natural science. Like mathematicians, programmers
-use formal languages to denote ideas (specifically computations). Like engineers,
-they design things, assembling components into systems and evaluating tradeoffs
-among alternatives. Like scientists, they observe the behavior of complex systems,
-form hypotheses, and test predictions.
-
-Writing computer programs requires not only mechanistic thinking but creative
-problem solving. Problem solving means the ability to formulate problems, think
-creatively about solutions, and express a solution clearly and accurately. As
-it turns out, the process of learning to program is an excellent opportunity to
-practice problem solving skills. That's why this chapter is called, *The Way of
-the Program*.
-
-On one level, you will be learning to program, a useful skill by itself. On
-another level, you will use programming as a means to an end. As we go along,
-that end will become clearer.
-
-
-.. index:: programming language, portable, high-level language,
- low-level language, compile, interpret
-
diff --git a/_sources/GeneralIntro/toctree.rst b/_sources/GeneralIntro/toctree.rst
deleted file mode 100644
index de8d6027..00000000
--- a/_sources/GeneralIntro/toctree.rst
+++ /dev/null
@@ -1,22 +0,0 @@
-General Introduction
-::::::::::::::::::::
-
-.. toctree::
- :caption: General Introduction
- :maxdepth: 2
-
- intro-TheWayoftheProgram.rst
- Algorithms.rst
- ThePythonProgrammingLanguage.rst
- SpecialWaystoExecutePythoninthisBook.rst
- MoreAboutPrograms.rst
- FormalandNaturalLanguages.rst
- ATypicalFirstProgram.rst
- WhatisDebugging.rst
- Syntaxerrors.rst
- RuntimeErrors.rst
- SemanticErrors.rst
- ExperimentalDebugging.rst
- Comments.rst
- Glossary.rst
-
\ No newline at end of file