6.3 the Fundamental Questions 6.3.1 Name Binding and Scope Names In

Total Page:16

File Type:pdf, Size:1020Kb

6.3 the Fundamental Questions 6.3.1 Name Binding and Scope Names In 6.3 The Fundamental Questions 6.3.1 Name Binding and Scope Names in Prolog are used to represent predicates and terms. Predicates are used to express a relationship between terms. For example, the statement below could represent the relationship that Jay is the father of Baron. (It could just as well represent the relationship that Baron is the father of Jay since the father predicate has no intrinsic meaning in Prolog.) This is the simplest type of statement and is known as a fact. The name father is the predicate used in this fact. father(jay, baron). Predicates are also used in rules, which define new relationships in terms of existing relationships. For example, the statement below defines the sibling relationship: X and Y are siblings if they have the same father and X is not equal to Y. The predicates in this example are sibling , father, \+ (not) and = (equal). The left side of the :- (pronounced “if”) operator is called the head of the rule; the right side is called the body. The comma separated terms on the right side are called the conditions of the rule. sibling(X, Y) :- father(Z, X), father(Z, Y), \+(X = Y). The Prolog term is the single data structure in the language. Terms are either atoms, numbers, variables or compound terms. An atom is a name with no intrinsic meaning that is used to represent a constant value in the domain. An atom is a sequence of alphanumeric characters beginning with a lower case letter or a sequence of characters enclosed in single quotes. Examples of atoms include: jay ‘Jay Fenwick’ x ‘some $’ Notice that enclosing a sequence of characters in single quotes allows us to have constants in our domain that start with an upper case letter and/or include non-alphanumeric characters. Numbers can also be the terms of predicates. For example, a multiplication table can be expressed with a series of statements of the following form: multiply(1, 1, 1). multiply(1, 2, 2). multiply(1, 3, 3). Variables are represented by a sequence of letters, numbers and underscores, starting with either an upper case letter or an underscore. A single underscore is a special type of variable, known as the anonymous variable. As seen in the previous section, variables are used in rules or queries and are instantiated during the inferencing process except for the anonymous variable that is used in the pattern matching, but not instantiated. A variable can be instantiated to any term, including atoms, numbers, compound terms and other variables. Example of variables include: X Thefather _father _ A compound term is either a list or a functor term. A Prolog list consists of elements separated by commas enclosed in square brackets. Examples of Prolog lists can be seen below; the first list is the empty list or nil. [] [a, b, c] [a, [b]] [1, a, [‘hello’]] A string, enclosed in double quotes rather than single quotes, is actually equivalent to a list of the encoded value of the characters within the string. This can be seen by the example below. The = operator attempts to unify the term on the left with the term on the right and does so by instantiating X, Y, Z to the ascii codes for a, b, and c, respectively. | ?- "abc" = [X, Y, Z]. X = 97 Y = 98 Z = 99 yes A functor term is composed of an atom, known as a functor, and a number of argument terms enclosed within parenthesis. A functor term looks like a function call, however, no transfer of control occurs; rather a functor term, like an atom, is used to represent some value in the domain. Consider the example below. The first three facts represent father-son relationships between the first argument of the predicate and the second. fatherof(‘Baron’) does not evaluate to another value; it is simply a value in the domain, much like ‘Baron’, ‘Grayson’ and ‘Ethan’ are values in the domain. Note that the single quotes are used with ‘Baron’, ‘Grayson’, and ‘Ethan’ to prevent these atoms from being treated as variables. The rule can be used to identify sibling relationships, for example, determining that ‘Baron’ and ‘Grayson’ are siblings. father('Baron', fatherof('Baron')). father('Grayson', fatherof('Baron')). father('Ethan', fatherof('Baron')). sibling(X, Y) :- father(X, Z), father(Y, Z), \+(X = Y). A procedure in Prolog is a set of statements whose head begins with the same predicate. For example, the set of statements below is a Prolog procedure. myappend([], L, L). myappend([H|T], L, [H|R]) :- myappend(T, L, R). Prolog performs static scoping and the scope of a Prolog variable is the statement in which the variable appears. For example, the scope of the variable L in the first myappend statement is only that myappend statement. The variable L in the second statement is unrelated to the variable L in the first statement. (If you want to relate this to the block scoping of imperative languages, each statement would be equivalent to a block.) As noted earlier, each call to the procedure will result in a set of variables allocated for that procedure call. The second myappend rule may be used multiple times in the attempt to solve a myappend query. Each use of the rule will result in the creation of space for the rule variables. Thus, the instantiation of L in one use of the rule will be different than the instantiation of L in a second use of the rule. Prolog is dynamically typed, which means that the type errors are not detected until runtime. If a function is applied to a term with an invalid type, then Prolog will report the error when the function is applied. Unlike most languages, Prolog does not detect the use of a predicate with the wrong number of parameters as a type error. Instead, Prolog searches for a predicate with the given arity and reports that a predicate with that arity is undefined. Current implementations of Prolog compilers typically target the Warren Abstract Machine (WAM). Similar to the implementation of imperative languages, the WAM uses one or more stacks to store variables and control information, a heap area for data values and an area called the trail to hold information for restoring values when backtracking occurs. These data areas grow while the resolution process creates more subgoals to prove and shrink during backtracking. Space is automatically allocated as needed and garbage collection is performed by the interpreter to reclaim space that is no longer needed. 6.3.2 Expressions Prolog statements, or expressions, are the equivalent of Horn clauses. A Horn clause is a clause in one of the following two forms (P1 ^ P2 ^ … ^ Pn) -> Q (R1 ^ R2 ^ … ^ Rn) These would be written in Prolog in the form below. The Q predicate expression is known as a rule. The Ri predicates are called facts. Q :- P1, P2, …, Pn. R1. R2. Rn. Thus the Prolog :- operator is logically equivalent to implication and the comma is equivalent to logical and. Prolog also defines the ; operator to be equivalent to logical or. For example, the expression below is equivalent to Q if P1 or P2 Q :- P1; P2. The statement above is equivalent to two below. Q :- P1. Q :- P2. The , operator has higher precedence than the; operator, thus the statement below: Q :- P1, P2; P3, P4. Is equivalent to: Q :- P1, P2. Q :- P3, P4. Parenthesis can be used to change the precedence. For example, Q :- P1, (P2 ; P3), P4. is logically equivalent to Q :- P1, P2, P4. Q :- P1, P3, P4. Prolog expressions can also consist of arithmetic operators and comparison operators that have the expected precedence (for example, comparison operators have a higher precedence than arithmetic operators, / and * have higher precedence than + and -). In addition, Prolog provides a set of equality and inequality operators and an is operator that evaluates its right operand and attempts to unify the value with the left operand. The is operator can be used to instantiate variables, somewhat similar to assignment statements in imperative languages. Descriptions and example uses of these operators can be seen in the table below. Operator Description Examples is Evaluates the expression on the | ?- X is 3. right and determines whether it can X = 3 be unified with the expression on yes the left. The expression on the left | ?- 3 is 3. is not evaluated, thus the last yes example evaluates to no. | ?- 3 + 4 is 3 + 4. no =, \= Determines whether the left operand | ?- [X, Y] = [a, b]. and the right operand can or can not X = a be unified Y = b Yes | ?- X = 3. X = 3 yes | ?- X = Y. Y = X yes ==, \== Determines whether the left and | ?- X == 3. right operands evaluate to the same no values. In the first example, X is | ?- 3 * 4 == 3 * 4. unbound and thus has no value. yes | ?- X is 3, X == 3. X = 3 yes <, >, Comparison operators. Notice the | ?- 5 >= 4. =<, >= less than or equal to operator is =< yes | ?- X is 4, 3 =< X. X = 4 yes /, * Operators for division and | ?- X is 2 * 3, 10 > X. multiplication X = 6 yes | ?- X is 3, Y is 10/X. X = 3 Y = 3.3333333333333335 yes +, - Operators for addition and | ?- X is 3, Y is 4 - X + subtraction 7. X = 3 Y = 8 yes Prolog also supplies a number of built-in predicates. For example, the atom predicate evaluates to true if its argument is an atom. | ?- atom(hello). yes | ?- atom('hello'). yes | ?- atom("hello"). no | ?- atom(3). no In fact, the operators described earlier are simply predicates that have been invoked using infix, rather than prefix, notation.
Recommended publications
  • Chapter 5 Names, Bindings, and Scopes
    Chapter 5 Names, Bindings, and Scopes 5.1 Introduction 198 5.2 Names 199 5.3 Variables 200 5.4 The Concept of Binding 203 5.5 Scope 211 5.6 Scope and Lifetime 222 5.7 Referencing Environments 223 5.8 Named Constants 224 Summary • Review Questions • Problem Set • Programming Exercises 227 CMPS401 Class Notes (Chap05) Page 1 / 20 Dr. Kuo-pao Yang Chapter 5 Names, Bindings, and Scopes 5.1 Introduction 198 Imperative languages are abstractions of von Neumann architecture – Memory: stores both instructions and data – Processor: provides operations for modifying the contents of memory Variables are characterized by a collection of properties or attributes – The most important of which is type, a fundamental concept in programming languages – To design a type, must consider scope, lifetime, type checking, initialization, and type compatibility 5.2 Names 199 5.2.1 Design issues The following are the primary design issues for names: – Maximum length? – Are names case sensitive? – Are special words reserved words or keywords? 5.2.2 Name Forms A name is a string of characters used to identify some entity in a program. Length – If too short, they cannot be connotative – Language examples: . FORTRAN I: maximum 6 . COBOL: maximum 30 . C99: no limit but only the first 63 are significant; also, external names are limited to a maximum of 31 . C# and Java: no limit, and all characters are significant . C++: no limit, but implementers often impose a length limitation because they do not want the symbol table in which identifiers are stored during compilation to be too large and also to simplify the maintenance of that table.
    [Show full text]
  • A Concurrent PASCAL Compiler for Minicomputers
    512 Appendix A DIFFERENCES BETWEEN UCSD'S PASCAL AND STANDARD PASCAL The PASCAL language used in this book contains most of the features described by K. Jensen and N. Wirth in PASCAL User Manual and Report, Springer Verlag, 1975. We refer to the PASCAL defined by Jensen and Wirth as "Standard" PASCAL, because of its widespread acceptance even though no international standard for the language has yet been established. The PASCAL used in this book has been implemented at University of California San Diego (UCSD) in a complete software system for use on a variety of small stand-alone microcomputers. This will be referred to as "UCSD PASCAL", which differs from the standard by a small number of omissions, a very small number of alterations, and several extensions. This appendix provides a very brief summary Of these differences. Only the PASCAL constructs used within this book will be mentioned herein. Documents are available from the author's group at UCSD describing UCSD PASCAL in detail. 1. CASE Statements Jensen & Wirth state that if there is no label equal to the value of the case statement selector, then the result of the case statement is undefined. UCSD PASCAL treats this situation by leaving the case statement normally with no action being taken. 2. Comments In UCSD PASCAL, a comment appears between the delimiting symbols "(*" and "*)". If the opening delimiter is followed immediately by a dollar sign, as in "(*$", then the remainder of the comment is treated as a directive to the compiler. The only compiler directive mentioned in this book is (*$G+*), which tells the compiler to allow the use of GOTO statements.
    [Show full text]
  • Concise Introduction to C++
    i i final3 2012/4/19 page 47 i i Chapter 2 Concise Introduction to C++ C++ seems to be most suitable for many practical applications. Indeed, C++ is sufficiently high-level to allow transparent object-oriented programming and efficient use of human resources, yet is also sufficiently low-level to have types, variables, pointers, arrays, and loops to allow efficient use of computer resources. In this chapter, we give a concise description of C++ and illustrate its power as an object-oriented programming language. In particular, we show how to construct and use abstract mathematical objects such as vectors and matrices. We also explain the notion of a template class, which can be filled with a concrete type later on in compilation time. We also discuss inheritance and illustrate its potential. 2.1 Objects As we have seen above, C is a language based on functions. Every command is also a function that returns a value that can be further used or abandoned, according to the wish of the programmer. Furthermore, programmers can write their own functions, which may also return variables of the type specified just before the function name. When the function is called, a temporary, unnamed variable is created to store the returned value until it has been used. C++, on the other hand, is an object-oriented programming language. In this kind of language, the major concern is not the functions that can be executed but rather the objects upon which they operate. Although C++ supports all the operations and features available in C, its point of view is different.
    [Show full text]
  • Concepts in Programming Languages Practicalities
    Concepts in Programming Languages Practicalities I Course web page: Alan Mycroft1 www.cl.cam.ac.uk/teaching/1617/ConceptsPL/ with lecture slides, exercise sheet and reading material. These slides play two roles – both “lecture notes" and “presentation material”; not every slide will be lectured in Computer Laboratory detail. University of Cambridge I There are various code examples (particularly for 2016–2017 (Easter Term) JavaScript and Java applets) on the ‘materials’ tab of the course web page. I One exam question. www.cl.cam.ac.uk/teaching/1617/ConceptsPL/ I The syllabus and course has changed somewhat from that of 2015/16. I would be grateful for comments on any remaining ‘rough edges’, and for views on material which is either over- or under-represented. 1Acknowledgement: various slides are based on Marcelo Fiore’s 2013/14 course. Alan Mycroft Concepts in Programming Languages 1 / 237 Alan Mycroft Concepts in Programming Languages 2 / 237 Main books Context: so many programming languages I J. C. Mitchell. Concepts in programming languages. Cambridge University Press, 2003. Peter J. Landin: “The Next 700 Programming Languages”, I T.W. Pratt and M. V.Zelkowitz. Programming Languages: CACM (published in 1966!). Design and implementation (3RD EDITION). Some programming-language ‘family trees’ (too big for slide): Prentice Hall, 1999. http://www.oreilly.com/go/languageposter http://www.levenez.com/lang/ ? M. L. Scott. Programming language pragmatics http://rigaux.org/language-study/diagram.html (4TH EDITION). http://www.rackspace.com/blog/ Elsevier, 2016. infographic-evolution-of-computer-languages/ I R. Harper. Practical Foundations for Programming Plan of this course: pick out interesting programming-language Languages.
    [Show full text]
  • Java Terms/Concepts You Should Know from OOPDA Glossary Terms
    Java Terms/Concepts You Should Know from OOPDA A abstract class A class with the abstract reserved word in its header. Abstract classes are distinguished by the fact that you may not directly construct objects from them using the new operator. An abstract class may have zero or more abstract methods. abstract method A method with the abstract reserved word in its header. An abstract method has no method body. Methods defined in an interface are always abstract. The body of an abstract method must be defined in a sub class of an abstract class, or the body of a class implementing an interface. Abstract Windowing Toolkit The Abstract Windowing Toolkit (AWT) provides a collection of classes that simplify the creation of applications with graphical user interfaces. These are to be found in the java.awt packages. Included are classes for windows, frames, buttons, menus, text areas, and so on. Related to the AWT classes are those for the Swing packages. aggregation A relationship in which an object contains one or more other subordinate objects as part of its state. The subordinate objects typically have no independent existence separate from their containing object. When the containing object has no further useful existence, neither do the subordinate objects. For instance, a gas station object might contain several pump objects. These pumps will only exist as long as the station does. Aggregation is also referred to as the has-a relationship, to distinguish it from the is-a relationship, which refers to inheritance. anonymous class A class created without a class name.
    [Show full text]
  • Intel ® Fortran Programmer's Reference
    ® Intel Fortran Programmer’s Reference Copyright © 1996-2003 Intel Corporation All Rights Reserved Issued in U.S.A. Version Number: FWL-710-02 World Wide Web: http://developer.intel.com Information in this document is provided in connection with Intel products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. EXCEPT AS PROVIDED IN INTEL’S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSO- EVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PAR- TICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. Intel products are not intended for use in medical, life saving, or life sustaining applications. This Intel® Fortran Programmer’s Reference as well as the software described in it is furnished under license and may only be used or copied in accordance with the terms of the license. The information in this manual is furnished for infor- mational use only, is subject to change without notice, and should not be construed as a commitment by Intel Corpora- tion. Intel Corporation assumes no responsibility or liability for any errors or inaccuracies that may appear in this document or any software that may be provided in association with this document. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "unde- fined." Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibil- ities arising from future changes to them.
    [Show full text]
  • PHP Advanced and Object-Oriented Programming
    VISUAL QUICKPRO GUIDE PHP Advanced and Object-Oriented Programming LARRY ULLMAN Peachpit Press Visual QuickPro Guide PHP Advanced and Object-Oriented Programming Larry Ullman Peachpit Press 1249 Eighth Street Berkeley, CA 94710 Find us on the Web at: www.peachpit.com To report errors, please send a note to: [email protected] Peachpit Press is a division of Pearson Education. Copyright © 2013 by Larry Ullman Acquisitions Editor: Rebecca Gulick Production Coordinator: Myrna Vladic Copy Editor: Liz Welch Technical Reviewer: Alan Solis Compositor: Danielle Foster Proofreader: Patricia Pane Indexer: Valerie Haynes Perry Cover Design: RHDG / Riezebos Holzbaur Design Group, Peachpit Press Interior Design: Peachpit Press Logo Design: MINE™ www.minesf.com Notice of Rights All rights reserved. No part of this book may be reproduced or transmitted in any form by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. For information on getting permission for reprints and excerpts, contact [email protected]. Notice of Liability The information in this book is distributed on an “As Is” basis, without warranty. While every precaution has been taken in the preparation of the book, neither the author nor Peachpit Press shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the instructions contained in this book or by the computer software and hardware products described in it. Trademarks Visual QuickPro Guide is a registered trademark of Peachpit Press, a division of Pearson Education. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks.
    [Show full text]
  • Software II: Principles of Programming Languages Control Statements
    Software II: Principles of Programming Languages Lecture 8 – Statement-Level Control Structures Control Statements: Evolution • FORTRAN I control statements were based directly on IBM 704 hardware • Much research and argument in the 1960s about the issue – One important result: It was proven that all algorithms represented by flowcharts can be coded with only two-way selection and pretest logical loops Control Structure • A control structure is a control statement and the statements whose execution it controls • Design question – Should a control structure have multiple entries? Selection Statements • A selection statement provides the means of choosing between two or more paths of execution • Two general categories: – Two-way selectors – Multiple-way selectors Two-Way Selection Statements • General form: if control_expression then clause else clause • Design Issues: – What is the form and type of the control expression? – How are the then and else clauses specified? – How should the meaning of nested selectors be specified? The Control Expression • If the then reserved word or some other syntactic marker is not used to introduce the then clause, the control expression is placed in parentheses • In C89, C99, Python, and C++, the control expression can be arithmetic • In most other languages, the control expression must be Boolean Clause Form • In many contemporary languages, the then and else clauses can be single statements or compound statements • In Perl, all clauses must be delimited by braces (they must be compound) • In Fortran
    [Show full text]
  • Software II: Principles of Programming Languages Introduction
    Software II: Principles of Programming Languages Lecture 5 – Names, Bindings, and Scopes Introduction • Imperative languages are abstractions of von Neumann architecture – Memory – Processor • Variables are characterized by attributes – To design a type, must consider scope, lifetime, type checking, initialization, and type compatibility Names • Design issues for names: – Are names case sensitive? – Are special words reserved words or keywords? Names (continued) • Length – If too short, they cannot be connotative – Language examples: • FORTRAN 95: maximum of 31 (only 6 in FORTRAN IV) • C99: no limit but only the first 63 are significant; also, external names are limited to a maximum of 31 (only 8 are significant K&R C ) • C#, Ada, and Java: no limit, and all are significant • C++: no limit, but implementers often impose one Names (continued) • Special characters – PHP: all variable names must begin with dollar signs – Perl: all variable names begin with special characters, which specify the variable’s type – Ruby: variable names that begin with @ are instance variables; those that begin with @@ are class variables Names (continued) • Case sensitivity – Disadvantage: readability (names that look alike are different) • Names in the C-based languages are case sensitive • Names in others are not • Worse in C++, Java, and C# because predefined names are mixed case (e.g. IndexOutOfBoundsException ) Names (continued) • Special words – An aid to readability; used to delimit or separate statement clauses • A keyword is a word that is special only
    [Show full text]
  • Names and Binding
    Names, Bindings, and Scopes Alark Joshi Introduction • Imperative languages are abstractions of von Neumann architecture o Memory o Processor • Variables characterized by attributes o To design a type, must consider scope, lifetime, type checking, initialization, and type compatibility 1-2 Copyright © 2009 Addison-Wesley. All rights reserved. Names • Design issues for names: o Are names case sensitive? o Are special words reserved words or keywords? 1-3 Copyright © 2009 Addison-Wesley. All rights reserved. Names (continued) • Length o If too short, they cannot be connotative o Language examples: • FORTRAN 95: maximum of 31 • C99: no limit but only the first 63 are significant; also, external names are limited to a maximum of 31 • C#, Ada, and Java: no limit, and all are significant • C++: no limit, but implementers often impose one 1-4 Copyright © 2009 Addison-Wesley. All rights reserved. Names (continued) • Special characters o PHP: all variable names must begin with dollar signs o Perl: all variable names begin with special characters, which specify the variable’s type o Ruby: variable names that begin with @ are instance variables; those that begin with @@ are class variables 1-5 Copyright © 2009 Addison-Wesley. All rights reserved. Names (continued) • Case sensitivity o Disadvantage: readability (names that look alike are different) • Names in the C-based languages are case sensitive • Names in others are not • Worse in C++, Java, and C# because predefined names are mixed case (e.g. IndexOutOfBoundsException) 1-6 Copyright © 2009 Addison-Wesley. All rights reserved. Names (continued) • Special words o An aid to readability; used to delimit or separate statement clauses • A keyword is a word that is special only in certain contexts, e.g., in Fortran o Real VarName (Real is a data type followed with a name, therefore Real is a keyword) o Real = 3.4 (Real is a variable) 1-7 Copyright © 2009 Addison-Wesley.
    [Show full text]
  • C Identifiers
    C++ Identifiers and Datatypes Each line of a C++ program contains a number of different words. The C++ compiler classifies these words into different categories: Reserved words: A reserved is a word that has a special meaning in C++. A reserved word always appears in lowercase and can only be used for the purpose, which has been defined to it by the C++ compiler. Examples of reserved words: int, void, return. The other types of words are identifiers that come into two varieties: standard and user defined. Standard Identifiers: Standard identifiers have a special meaning in C++. They are the names of operations defined in the standard C++ library. For example: cout is the name of an I/O operation. Unlike reserved words, standard identifiers can be redefined and used by the programmer for other purposes. However, this is NOT recommended. User-defined Identifiers: We choose our own identifiers (called user-defined identifier) to name memory cells that will hold data and program results and to name operations that we define. These names should follow specific rules to be acceptable to the C++ compiler. The rules that make up for a valid identifier are: An identifier must consist of only letters, digits and underscores. An identifier cannot begin with a digit A C++ reserved word cannot be used as an identifier. An identifier defined in the C++ standard library should not be redefined. Some C++ compilers only consider identifiers up to 31 characters. Uppercase and Lowercase: C++ is case sensitive. This means that it distinguishes between small and capital letters.
    [Show full text]
  • {PDF} Head First Javascript Programming
    HEAD FIRST JAVASCRIPT PROGRAMMING PDF, EPUB, EBOOK Eric Freeman,Elisabeth Robson | 704 pages | 13 Jun 2014 | O'Reilly Media, Inc, USA | 9781449340131 | English | Sebastopol, United States Head First JavaScript Programming PDF Book You know the saying: There's no time like the present Then the rest of the book went back to basic OO concepts such as dog inheritance hierarchies. It is more focused on giving you a foundation in JavaScript programming than it is teaching you how to add JavaScript to webpages. Q: Is JavaScript case sensitive? Details if other :. Enabling JavaScript in your browser will allow you to experience all the features of our site. This was the case with early JavaScript, and was why, for many years, the performance of JavaScript was not so great. Many people who feel they are good at JS, will feel left behind after reading this book. A: Only by name. Who we are!? Showing Is it? It gets very overwhelming to go through the plethora of websites and ebooks and this book gives the programming noob real structure that can be followed and is very logically sequenced and organized. JavaScript is pass-by-value. A lot of the JavaScript instructional material I had been using earlier was fine at instructing me in the use of the language but did absolutely nothing to show me actually how to integrate it into client-side programming. Just keep learning. But if you wanna do all that you have to know JavaScript. Jun 01, Carl Klutzke rated it really liked it Shelves: recommended-non-fiction.
    [Show full text]