DOCSLIB.ORG

Object-Oriented Programming with PHP

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Object-Oriented Programming with PHP Object-oriented Programming with PHP This chapter introduces the readers to the basic features of object-oriented programming with PHP and then provides an overview of the common design patterns. Later, we will go over how error handling and exception handling are performed in PHP. PHP has traditionally not been an object-oriented programming (OOP) language until PHP 5 when the language was revamped for a great deal to support the OOP features. PHP in programming PHP is a scripting language that is often used to build dynamic web applications. PHP inherits its programming style from C and Java. PHP comes with powerful libraries and strong community support, making it one of the favorite languages that developers use for building web applications. We will be utilizing the PHP libraries that were installed in Bonus chapter 1, Installation of PHP, MariaDB, and Apache to execute our scripts. Let us look at the three ways in which PHP scripts can be executed: • Via the PHP shell • Via the command line • Using a web server such as Apache The PHP shell is commonly used as a playground to test small scripts, and the shell can get tedious when working with bigger scripts. Executing files via command line is the second option where the PHP scripts will live inside the files. As we will be using object-oriented design to build our scripts, we will skip the first method and use the second and third methods to execute our scripts. Object-oriented Programming with PHP Object-oriented programming Object-oriented programming is a popular programming paradigm where concepts are grouped into reusable objects that carry their own attributes and behaviors. An attribute can be described as a variable that is in the object, which is used to hold data pertaining to that object, while a behavior describes what an object can do. Let us consider the example of a User object; a user will have a name, an age, and an address, and these will be the attributes for a user. As the User object stores the address, we could have a behavior to allow and facilitate address retrieval; the behaviors are referred to as class methods. An object is a complex data structure that can have one or more types of attributes and one or more types of behaviors. The attributes and behaviors are defined in a class, and an object is an instance of a class. Therefore, the instances carry the same attributes and behaviors of that class. Though there could be multiple objects of the same class, the data stored in each object would be stored in different memory locations. OOP is not a new concept and has been around for a very long period. OOP allows us to group our code based on behaviors and attributes and also allows us to organize our code for better reusability. Basic object-oriented features such as objects and classes were introduced into PHP 3 in 1998. In 2000, PHP 4 was released with a better support for object-oriented features but the implementation of objects was still an issue, as the object referencing was handled similar to value types. So a whole object would be copied when an object had to be passed in as a parameter to a function. As the object had to be copied, recreated, and stored several times, this led to poor scalability for big applications, extra usage of memory, and unnecessary overhead on the resources. PHP 5, which was shipped in 2004, arrived with a far superior object model that was better at handling objects, thereby increasing the performance and scalability of the web applications. Now that we have a basic idea about OOP, let us dive into understanding classes and objects. Sublime text is used as the text editor for this series. It is recommended to use a text editor or IDE of your choice. A few popular IDEs are Eclipse for PHP and the NetBeans IDE for PHP development. Classes and objects In our first example, let us define a class. For creating a class, we would at least need one piece of information, the unique name for the class. In PHP, a class definition begins with the keyword class, and the keyword is followed by the unique name of the class. This is followed by a pair of curly braces and any class attributes and/or methods are enclosed into these curly braces. [ 2 ] Bonus chapter 2 There are two rules for naming a class in PHP mentioned as follows: • It should begin with a letter or an underscore • It can only contain letters, numbers, or underscores It is a good practice to have the name of the class as part of the filename (for example, class.Students.php) or the actual filename itself (for example, Students.php). It is also common to use camel case, which is a common practice for naming the classes, class attributes, and class methods where multiple words are compounded into one, and the first letter of each word is written in upper case. Consider the following code snippet as an example showing a Students class: <?php class Students { public function __construct() /** * Code to be executed *upon object instantiation */ } } ?> In this example, we are creating a Students class with a constructor using the __construct keyword. A constructor is the first function that is triggered upon the object instantiation. A constructor is commonly used for any bootstrapping purposes such as importing configurations and/or performing setup operations. The __construct() keyword is reserved by the PHP engine to identify the constructors in a class. Therefore, a constructor cannot be declared outside a class. The PHP engine treats a constructor like any other function; so, if a constructor is declared more than once, we will receive an error. Now that we understand how to create a class, let us continue with our Students class and add a few class attributes and class methods. After adding the attributes and methods, let us instantiate an object to access the attributes and methods. To instantiate an object, we will use the new keyword. We would need at least two pieces of information for the object instantiation; the first piece is the name of the object and the second is the name of class for which an object is being instantiated. Consider the following code example: <?php class Students { [ 3 ] Object-oriented Programming with PHP public $first_name; public $last_name; public $address; public function __construct($first_name , $last_name, $address){ $this->first_name = $first_name; $this->last_name = $last_name; $this->address = $address; } public function greeting(){ return "Hello ".$this->first_name."\n"; } public function getAddress(){ return $this->address."\n"; } } $student = new Students("John", "Doe", "3225 Woodland Park St"); echo $student->greeting(); echo $student->getAddress(); ?> In this example, we have added three class attributes or properties to store the first name, the last name, and the address of the student. We are initializing our properties via the constructor and the value for our properties will be passed in after the object instantiation. We have also added two class methods that would print out a greeting and return the address of the student. We are using the $this keyword to access our properties, and it can also be used to access the class methods as it is a reference to the Students object. We are using the -> notation to access the properties or the methods of a class. After defining the class, we are instantiating an object of the Students class, and are calling the $student object. During the instantiation, we are passing in the arguments that are expected by our constructor, and these values are assigned to the properties. After the object instantiation, we are invoking the class methods using our $student object. [ 4 ] Bonus chapter 2 The output for the previous code will be as follows: Hello John 3225 Woodland Park St Static properties and methods It is not always necessary to instantiate an object to access the properties or methods of a class. A class can also have static methods and properties that are bound to the class, rather than the object. To access a static method or a static property, we will use the scope resolution operator (::). To create a static property or static method, we will append the static keyword ahead of the variable. A static property or method will be commonly used to instantiate a database connection or a connection to a remote service that can add significant overhead. For a method to be accessible, the object of the class has to be created, during which a virtual method and member table are created for that class. While accessing static methods, we can avoid this overhead of creating a virtual method and member table for the class. Static methods are commonly used for high-performance systems. We have successfully built our first class, instantiated the class, accessed the class methods, and discussed static methods and properties. During this process, we have already come across one of the four principles of OOP, which is abstraction. Abstraction is a concept about exposing the behavior and properties and hiding the particular code that performs that behavior. In our previous example, we have abstracted all the functionalities that a student object can have into the Students class, and have accessed those functionalities by creating an object of that class. The other three principles that we would look at are encapsulation, inheritance, and polymorphism. Encapsulation With abstraction, we have seen how to hide the underlying implementation that provides properties and methods. With encapsulation, let us see how we can expose a specific set of methods and properties, while hiding or restricting access to another set of properties and/or methods based on who is accessing this functionality.
Load more

Recommended publications
  • Operator Overloading ______
    Chapter 10: Operator Overloading _________________________________________________________________________________________________________ Consider the following C++ code snippet: vector<string> myVector(kNumStrings); for(vector<string>::iterator itr = myVector.begin(); itr != myVector.end(); ++itr) *itr += "Now longer!"; Here, we create a vector<string> of a certain size, then iterate over it concatenating “Now longer!” to each of the strings. Code like this is ubiquitous in C++, and initially does not appear all that exciting. However, let's take a closer look at how this code is structured. First, let's look at exactly what operations we're performing on the iterator: vector<string> myVector(kNumStrings); for(vector<string>::iterator itr = myVector.begin(); itr != myVector.end(); ++itr) *itr += "Now longer!"; In this simple piece of code, we're comparing the iterator against myVector.end() using the != operator, incrementing the iterator with the ++ operator, and dereferencing the iterator with the * operator. At a high level, this doesn't seem all that out of the ordinary, since STL iterators are designed to look like regular pointers and these operators are all well-defined on pointers. But the key thing to notice is that STL iterators aren't pointers, they're objects, and !=, *, and ++ aren't normally defined on objects. We can't write code like ++myVector or *myMap = 137, so why can these operations be applied to vector<string>::iterator? Similarly, notice how we're concatenating the string “Now longer!” onto the end of the string: vector<string> myVector(kNumStrings); for(vector<string>::iterator itr = myVector.begin(); itr != myVector.end(); ++itr) *itr += "Now longer!"; Despite the fact that string is an object, somehow C++ “knows” what it means to apply += to strings.
    [Show full text]
  • Property Mapping: a Simple Technique for Mobile Robot Programming
    Property Mapping: a simple technique for mobile robot programming Illah R. Nourbakhsh The Robotics Institute, Carnegie Mellon University Pittsburgh, PA 15213 [email protected] Abstract In this paper we present robot observability as a The mobile robot programming problem is a software predictor for diagnostic transparency. Then, we present a engineering challenge that is not easily conquered using language-independent technique called property mapping contemporary software engineering best practices. We for constructing robot programs that are diagnostically propose robot observability as a measure of the diagnostic transparent and thereby achieve high degrees of transparency of a situated robot program, then describe reliability. property mapping as a simple, language-independent approach to implementing reliable robot programs by maximizing robot observability. Examples from real- The Robot Programming Problem world, working robots are given in Lisp and Java. A mobile robot is a situated automata, or a module that comprises one part of a closed system together with the Introduction environment. Fig. 1 shows the standard depiction of a robot, with its outputs labeled as actions and the outputs The recent availability of inexpensive, reliable robot of the environment in turn labeled as percepts. chassis (e.g. ActivMedia Pioneer, IS-Robotics Magellan, Nomad Scout) has broadened the accessibility of mobile robotics research. Because these robots consist of fixed E hardware out-of-the-box, this technology is shifting the actions A P percepts emphasis of mobile robot research from a joint hardware and software design process toward hardware-unaware R mobile robot programming. This is a software design problem, and yet software Figure 1: The standard view of an embedded robot engineering best practices are not very helpful.
    [Show full text]
  • C++ Properties -- a Library Solution
    Document Number: SC22/WG21/N1615=04-0055 Date: 2004-04-09 Author: Lois Goldthwaite Email: [email protected] C++ Properties -- a Library Solution N1600 is a summary of the "property" language extension that is proposed for C++/CLI. I can't help feeling that this is an effort to impose an alien idiom on C++. There is too much of "the compiler will perform black magic behind your back" in it. There are too many ways in which the programmer must be aware that some [pseudo-]data members must be handled in different ways from [real] data members. The C++/CLI draft spec (N1608)says in 8.8.4 and 18.4 that "A property is a member that behaves as if it were a field." I think "behaves" is absolutely the wrong word to use here. A property is behavior that pretends to be state. From an OO design point of view, I think this is A Bad Idea. Behaviour should be visible; state should not. Further on, the document continues, "the X and Y properties can be read and written as though they were fields. In the example above, the properties are used to implement data hiding within the class itself." The subtle advantage of "hiding" a private data member by treating it as a public data member escapes me. Properties are just syntactic saccharine for getter and setter member functions for individual fields. C++ experts have spent years trying to educate people NOT to use public data, to use member functions instead, and now we propose to introduce something that looks just like public data? Do we really want to try to teach people that public fields are still bad, but properties are good, even though they look just the same from outside the class? Moreover, these public fields have side effects! There is a danger that too many novice programmers will prototype their designs using public fields, with the intent of changing them to properties later, if and when it proves necessary, and the general quality of code will suffer because of it.
    [Show full text]
  • Property Conveyances As a Programming Language
    Property Conveyances as a Programming Language Shrutarshi Basu∗ Nate Foster James Grimmelmann Harvard University Cornell University Cornell Law School & Cornell Tech Cambridge, MA, USA Ithaca, NY, USA New York, NY, USA [email protected] [email protected] [email protected] Abstract 1 Introduction Anglo-American law enables property owners to split up Many legal issues depend on vague, open-ended standards. rights among multiple entities by breaking their ownership For example, nuisance law prohibits “unreasonable” interfer- apart into future interests that may evolve over time. The con- ence with neighbors’ use of land. What counts as “unreason- veyances that owners use to transfer and subdivide property able” depends on an eight-factor balancing test, and many of rights follow rigid syntactic conventions and are governed the individual factors are themselves vague and open-ended, by an intricate body of interlocking doctrines that determine including “the social value that the law attaches to the pri- their legal eect. These doctrines have been codied, but mary purpose of the conduct;” and “the suitability of the only in informal and potentially ambiguous ways. particular use or enjoyment invaded to the character of the This paper presents preliminary work in developing a locality.” [American Law Institute 1979] A lawyer who wants formal model for expressing and analyzing property con- to know whether a client’s cement plant will be considered veyances. We develop a domain-specic language capable a nuisance will have to research numerous previous cases, of expressing a wide range of conveyances in a syntax ap- gather extensive facts about the plant and its neighbors, and proximating natural language.
    [Show full text]
  • Dealing with Properties
    Dealing with Properties Martin Fowler [email protected] lmost every object you create needs properties: some statement about the object. A person may have a height, a company may have a CEO, a flight may have a flight Anumber. There are a number of ways to model properties. In this article I will explore some of these ways and when you may want to use them. I’ve often seen patterns touch on this subject, but they usually only cover part of the picture. Here I want to cover the issue more broadly to give a better discussion of the options. The most common, and the simplest case is to use a Fixed Property, that is just declare the attribute on the class. In the vast majority of cases that is all you need to do. Fixed properties begin to fail when you have a large amount of them, or you need to change them frequently, possibly at run time. These forces lead you to the varieties of Dynamic Property. All dynamic properties have the quality of a parameterized attribute where to query a property you need to use a query method with a parameter. The simplest of these is the Flexible Dynamic Property where the parameter is just a string. This makes it easy to define and use properties, but is difficult to control. If you need that control you can use a Defined Dynamic Property where your parameters must be instances of some class. A further step of control allows you to strongly type your dynamic property with a Typed Dynamic Property.
    [Show full text]
  • Alice Glossary
    Adventures in Alice Programming // Glossary of Useful Terms by Michael Marion // July 2012 Worlds, methods, functions, properties, variables - it’s pretty easy to get all of the terminology and concept matter confused when it comes to programming in Alice. To that point, we’ve developed this handy reference to use. Hopefully it helps you not to get mixed up. Enjoy! World A world in Alice encompasses everything. Just as we’d say that everyone and everything exists in our world in real life; every object, method, event, or anything else lies inside the world in Alice. The whole .a2w file represents the world. Object An object is just what it sounds like. Any sort of three-dimensional shape such as a person, animal, piece of furniture, building, or anything else of the sort in your world is an object. Most objects are added to the world via the Add Objects button, but some - the ground, camera, and light, for instance - are there by default. There are also two-dimensional objects such as text and billboards. Properties An object’s properties are also what they sound like. All objects have certain properties - whether or not they’re showing, their color, their position, and so forth. Color Defines the color of an object. There is a limited number of color choices in Alice, but it covers all primary colors and some extras, including red, blue, green, yellow, black, and cyan. To specify a white object, select “no color”. Opacity Defines the transparency of an object. Unlike isShowing, setting the opacity to a middle amount allows it to be only slightly transparent.
    [Show full text]
  • Operator Overloading in C Sharp with Simple Example
    Operator Overloading In C Sharp With Simple Example Clonic and thick-witted Stephan synopsize his lashkars violated commence laughably. Selig cosponsors his self-understanding refurbishes incompletely, but oculomotor Elias never supernaturalise so earthwards. Morning Robbie never spatted so ineptly or infract any instance detractingly. We will send you exclusive offers when we launch our new service. Even an instance of a class cannot access its private members. Overloading also has surprising ramifications. Net mvc with plus method overloading example overloads must have a simple examples and conceptual way they occur at times. The example with encapsulation comes in. Get in with implicit cast operator methods and examples of overloaded only overload resolution and commentary before. If a variety of ansi sql, if many various other. The example with it in a directional vector class methods in operations of examples of parameters, we avoid building reactive concurrent applications. It adds numbers, concatenates strings or delegates; indicates the sign of a number. In her sense, MATLAB can be used to rapidly prototype an algorithm. Operator specifies an object or two shift operator overloading and b are compiled for this website is only not change these arguments should be accessed from? The process four sections each implement one of different concrete classes. Calling a simple examples of creating an underscore followed if we can be completely new scheduling demands and meaningful. You can definitely overload Casting. This operator with operators, simple examples illustrate, most ad packages based off of operations. We offer such diverse selection of courses from leading universities and cultural institutions from around in world.
    [Show full text]
  • Oberon Script: a Lightweight Compiler and Runtime System for the Web
    Oberon Script: A Lightweight Compiler and Runtime System for the Web Ralph Sommerer1 1 Microsoft Research, 7 J J Thomson Avenue, Cambridge, United Kingdom [email protected] Abstract. Oberon Script is a scripting language and runtime system for build- ing interactive Web Client applications. It is based on the Oberon programming language and consists of a compiler that translates Oberon Script at load-time into JavaScript code, and a small runtime system that detects and compiles script sections written in Oberon Script. 1 Introduction Oberon is the name of a modular, extensible operating system for single user worksta- tions [19], and also of an object-oriented programming language specifically devel- oped to implement the former [17]. Although originally designed as the native operat- ing system for custom built workstations, Oberon was subsequently ported to various different computing platforms including personal computers [2][4] and Unix worksta- tions [1][14][15]. With the recent emergence and proliferation of sophisticated Web client applica- tions, the Web browser has become a computing platform on its own. It offers the Web application programmer scripting facilities to programmatically interact with a Web server, and to manipulate the Web page in-place and without reloading. It thus allows the construction of complex Web application user interfaces that are not lim- ited to the page-based hypertext model anymore. As the Web browser morphs into a runtime system and operating platform for Web client application, the question arises whether it can provide a suitable target platform for one more installment of Oberon, especially in light of all previous porting efforts that have shown Oberon’s demands of the host platform to be very limited.
    [Show full text]
  • Project Oberon the Design of an Operating System and Compiler
    1 Niklaus Wirth Jürg Gutknecht Project Oberon The Design of an Operating System and Compiler Edition 2005 2 Project Oberon Preface This book presents the results of Project Oberon, namely an entire software environment for a modern workstation. The project was undertaken by the authors in the years 1986-89, and its primary goal was to design and implement an entire system from scratch, and to structure it in such a way that it can be described, explained, and understood as a whole. In order to become confronted with all aspects, problems, design decisions and details, the authors not only conceived but also programmed the entire system described in this book, and more. Although there exist numerous books explaining principles and structures of operating systems, there is a lack of descriptions of systems actually implemented and used. We wished not only to give advice on how a system might be built, but to demonstrate how one was built. Program listings therefore play a key role in this text, because they alone contain the ultimate explanations. The choice of a suitable formalism therefore assumed great importance, and we designed the language Oberon as not only an effective vehicle for implementation, but also as a publication medium for algorithms in the spirit in which Algol 60 had been created three decades ago. Because of its structure, the language Oberon is equally well suited to exhibit global, modular structures of programmed systems. In spite of the small number of man-years spent on realizing the Oberon System, and in spite of its compactness letting its description fit a single book, it is not an academic toy, but rather a versatile workstation system that has found many satisfied and even enthusiastic users in academia and industry.
    [Show full text]
  • Object-Oriented Programming in Oberon-2
    Hanspeter Mössenböck Object-Oriented Programming in Oberon-2 Second Edition © Springer‐Verlag Berlin Heidelberg 1993, 1994 This book is out of print and is made available as PDF with the friendly permission of Springer‐Verlag Contents 1 Overview......................................................................................... 1 1.1 Procedure-Oriented Thinking............................................. 1 1.2 Object-Oriented Thinking .................................................... 2 1.3 Object-Oriented Languages................................................. 3 1.4 How OOP Differs from Conventional Programming...... 6 1.5 Classes as Abstraction Mechanisms ................................... 9 1.6 History of Object-Oriented Languages ............................ 11 1.7 Summary .............................................................................. 12 2 Oberon-2........................................................................................ 13 2.1 Features of Oberon-2 .......................................................... 14 2.2 Declarations ......................................................................... 14 2.3 Expressions .......................................................................... 16 2.4 Statements ............................................................................ 18 2.5 Procedures............................................................................ 19 2.6 Modules................................................................................ 21 2.7 Commands..........................................................................
    [Show full text]
  • Discovering Hidden Properties to Attack Node.Js Ecosystem
    Discovering Hidden Properties to Attack Node.js Ecosystem Feng Xiao, Jianwei Huang, Yichang Xiong, Guangliang Yang, Hong Hu, Guofei Gu, Wenke Lee #BHUSA @BLACKHATEVENTS Feng Xiao @f3ixiao • CS PhD student at Georgia Tech. • Vulnerability researcher. Develop tools to detect and exploit 0days. • Focus on web/application security, but also enjoy network security+ and virtualization security. +Hacking the Brain: Customize Evil Protocol to Pwn an SDN Controller. DEF CON 2018 #BHUSA @BLACKHATEVENTS Agenda • Hi, you’ve found some new Node.js vulnerabilities! what are they? • Sounds interesting, you’ve built bug finding tools? how does it work? • Cool. More details on the real-world impact? #BHUSA @BLACKHATEVENTS $ cat vuls.txt #BHUSA @BLACKHATEVENTS Background $ man node • A JavaScript runtime built on Chrome’s v8 engine. Apps AppApps Code Core Modules libuv … Node.js Operating System #BHUSA @BLACKHATEVENTS $ man node • A JavaScript runtime built on Chrome’s v8 engine. • Widely-used for deploying server-side programs and desktop apps. #BHUSA @BLACKHATEVENTS $ man node • A JavaScript runtime built on Chrome’s v8 engine. • Widely-used for deploying server-side programs and desktop apps. • Object sharing is a very popular communication method for Node.js web apps. Request parsing modules that convert input into objects. #BHUSA @BLACKHATEVENTS Object Sharing GET /update?age=23 Querystring-based Serialization Client-side JS {func: update, age: 23} JSON-based Serialization Node.js web #BHUSA @BLACKHATEVENTS What if we inject additional properties that are unexpected to the program? Hidden Property Abusing HPA leverages the widely-used data exchanging feature in Node.js (object sharing) to tamper or forge critical program states of Node.js applications.
    [Show full text]
  • A GROOVY Way to Enhance Your SAS Life
    Paper CT05 A GROOVY way to enhance your SAS life Karl Kennedy, GCE Solutions, Manchester, UK ABSTRACT PROC GROOVY is a relatively new (SAS® 9.3+) and little-known SAS procedure that can unleash the power of Apache's GROOVY language (Java™-syntax compatible object-oriented programming language) within your SAS environment. To display the power of PROC GROOVY two methods for producing a bookmarked PDF containing trial results (tables, figures, and listings) are described. The first method uses PROC GROOVY/Java while the second uses standard BASE SAS. The primary goal of this paper is to show that with minimal Java and PROC GROOVY knowledge the programming burden/complexity of the task can be greatly reduced, for example by removing the requirement to parse an RTF file. This is achieved by utilising Java's vast collection of Application Programming Interfaces (APIs). A secondary goal is to open the world of Java to SAS programmers. INTRODUCTION In Clinical Trial reporting it is often required to provide the analysis results (tables, figures, and listings (TFLs)) in one complete PDF document. In a previous role, a client made such a request at the end of the study and without any process in place to handle this request we had to investigate how to combine all the RTFs into one PDF document. Fortunately, an excellent paper “A SAS Macro Utility to Append SAS-Generated RTF Outputs and Create the Table of Contents” [1] describes how to append RTF tables and listings into one RTF document which could then be saved as a PDF file.
    [Show full text]