diff --git a/1 - Introduction/1.2 - Code Examples.tex b/1 - Introduction/1.2 - Code Examples.tex index 39f3bdb..c107d7e 100644 --- a/1 - Introduction/1.2 - Code Examples.tex +++ b/1 - Introduction/1.2 - Code Examples.tex @@ -1,9 +1,9 @@ -All code examples in this resource use a sudo language that is not meant to be run or compiled directly. +All code examples in this resource use a pseudo language that is not meant to be run or compiled directly. I have chosen to use this approach so that the concepts can be extracted and implemented in any language on any platform. By focusing on the concepts at hand rather than specific implementations I can focus on trying to present the material in a clear and easy to understand manner. \par -I will cover how to use the sudo language and how to translate it to a useable programming language +I will cover how to use the pseudo language and how to translate it to a useable programming language in the chapter \pigChapter{Getting Started} in the section titled \pigChapter{Sudo Language}. diff --git a/2 - Getting Started/1.1 - Choosing A Programming Language.tex b/2 - Getting Started/1.1 - Choosing A Programming Language.tex index bce7881..eededc8 100644 --- a/2 - Getting Started/1.1 - Choosing A Programming Language.tex +++ b/2 - Getting Started/1.1 - Choosing A Programming Language.tex @@ -21,7 +21,7 @@ strictly functional, strictly object-oriented or they offer the best of both wor The syntax of a language is very important when choosing a language. This is mainly going to be a personal preference. Personally, I like C style syntax languages like C, C++,Java, PHP, Javascript, etc. -Other people might prefer other languages because their use of other syntax styles, like the almost sudo code style of Python. +Other people might prefer other languages because their use of other syntax styles, like the almost pseudo code style of Python. Your personal preference will come with time as you move from one language to another and develop your own personal styles and preferences. \subsection{Platform} @@ -60,5 +60,5 @@ I want to try and keep some bias out so that this resource is as lanuage agnosti \\ If after doing some research you are still unsure which lanauge you want to use, especially for going through this resource try out Python. Python is available for every platform, or at least all of the ones I can think of. It is interpreted so you will not -have to wait for the program to compile. Lastly, its syntax is one of the closest to the sudo langauge which this resource +have to wait for the program to compile. Lastly, its syntax is one of the closest to the pseudo langauge which this resource uses extensively. diff --git a/2 - Getting Started/1.3 - Sudo Language.tex b/2 - Getting Started/1.3 - Pseudo Language.tex similarity index 90% rename from 2 - Getting Started/1.3 - Sudo Language.tex rename to 2 - Getting Started/1.3 - Pseudo Language.tex index eac5b0b..b093caf 100644 --- a/2 - Getting Started/1.3 - Sudo Language.tex +++ b/2 - Getting Started/1.3 - Pseudo Language.tex @@ -1,9 +1,9 @@ -For the code examples presented in this resource I am going to be using a sudo language. -The concept behind a sudo language is to be able to present programming concepts in a +For the code examples presented in this resource I am going to be using a pseudo language. +The concept behind a pseudo language is to be able to present programming concepts in a language agnostic form so that the concepts can be translated to your language of choice. \par -It is great that you have chosen lanauge X to use throughout this resource, but how is the sudo lanauge going to help you out? +It is great that you have chosen lanauge X to use throughout this resource, but how is the pseudo lanauge going to help you out? Well, let's look at two examples and I will show their implementation in a few different languages. Hopefully this will help you to understand how the language should be tanslated to others (especially if your language of choice is one that I use). @@ -88,15 +88,15 @@ class Example1{ } \end{lstlisting} -Notice that all of the actual examples end up looking about the same? This is the point of using the sudo language. This way I can discuss the core concepts of the lesson at hand and then those concepts can be directly applied to any language of your choice. +Notice that all of the actual examples end up looking about the same? This is the point of using the pseudo language. This way I can discuss the core concepts of the lesson at hand and then those concepts can be directly applied to any language of your choice. \par -Also, notice the Python implementation, it is almost line for line, word for word identical to the sudo language example. If you would like to choose a language closest to the sudo language, choose Python. +Also, notice the Python implementation, it is almost line for line, word for word identical to the pseudo language example. If you would like to choose a language closest to the pseudo language, choose Python. \subsection{Example 2} Now that we have looked at a fairly simple example above, lets take a look at a more complicated example. Do not be afraid if it does not make too much sense right now, but try and notice the similarities -between the sudo language and the actual code examples. +between the pseudo language and the actual code examples. @@ -255,7 +255,7 @@ else: \end{lstlisting} This example does a better job of showing how each language can tackle the concepts in a different manner but the core concepts -laid out by the sudo language can still be extrapolated and translated to each individual programming language; as long as the language supports the concepts. +laid out by the pseudo language can still be extrapolated and translated to each individual programming language; as long as the language supports the concepts. You may notice that I left out the implementation of C in this example. This is intentionally done because C does not support the use of classes and objects. There are ways of completing this example in C using structs but that is something that you should learn on your own. diff --git a/3 - Functional Programming/1.1 - Variables.tex b/3 - Functional Programming/1.1 - Variables.tex index 063493e..4c765d2 100644 --- a/3 - Functional Programming/1.1 - Variables.tex +++ b/3 - Functional Programming/1.1 - Variables.tex @@ -41,7 +41,7 @@ boolean = false Please keep in mind that each programming language supports different data types and you should research those types to better understand variables in that language. As well some programming languages that are strickly typed which requires us to define the data type of the -variable on declaration (unlike our sudo language). +variable on declaration (unlike our pseudo language). \subsection{Operators} diff --git a/Programming In General.pdf b/Programming In General.pdf index 71de4a5..3a9dc1c 100644 Binary files a/Programming In General.pdf and b/Programming In General.pdf differ