What is the usage of self in laravel
In laravel, the self keyword is used to replace the class name. It can refer to static member variables and static functions of the current class. It is also used to suppress polymorphic behavior. It can refer to functions of the current class instead of subclasses. Overridden implementation, self always points to the current class and class instance.
#The operating environment of this article: Windows 10 system, Laravel version 6, Dell G3 computer.
What is the usage of self in laravel
You cannot use this
to call non-member functions within a static member function, but you can use self
to call static members Function/variable/constant; other member functions can use self
to call static member functions and non-static member functions. As the discussion deepened, I discovered that self
is not that simple. In view of this, this article first compares and differentiates several keywords, and then summarizes the usage of self
. The difference between
and parent
, static
and this
If you want to fully understand self
, should be distinguished from parent
, static
and this
. Comparisons are made below. The distinction between
parent
##self and
parent is relatively easy:
parent refers to the parent class/ The hidden method (or variable) of the base class,
self refers to its own method (or variable). For example, calling the parent class constructor in the constructor:
class Base { public function __construct() { echo "Base contructor!", PHP_EOL; } } class Child { public function __construct() { parent::__construct(); echo "Child contructor!", PHP_EOL; } } new Child; // 输出: // Base contructor! // Child contructor!
static
static The general purpose is to modify the function or variable to make it a class function and Class variables can also modify variables within functions to extend their life cycle to the life cycle of the entire application. But it is related to
self It is a new use introduced since PHP 5.3: static delayed binding.
static, the belonging class can be dynamically determined at runtime. For example:
class Base { public function __construct() { echo "Base constructor!", PHP_EOL; } public static function getSelf() { return new self(); } public static function getInstance() { return new static(); } public function selfFoo() { return self::foo(); } public function staticFoo() { return static::foo(); } public function thisFoo() { return $this->foo(); } public function foo() { echo "Base Foo!", PHP_EOL; } } class Child extends Base { public function __construct() { echo "Child constructor!", PHP_EOL; } public function foo() { echo "Child Foo!", PHP_EOL; } } $base = Child::getSelf(); $child = Child::getInstance(); $child->selfFoo(); $child->staticFoo(); $child->thisFoo();
Base constructor! Child constructor! Base Foo! Child Foo! Child Foo!
self and
static is: for static member functions,
self points to the current class of the code,
static points to the calling class; for non-static member functions,
self suppresses polymorphism and points to the member function of the current class,
static is equivalent to
this, dynamically pointing to the function of the calling class. The three keywords
parent,
self, and
static are very interesting to look at together, pointing to the parent class, current class, and subclass respectively. , a bit like "past, present, future".
this
self and
this are the most discussed combinations and are also the most likely to be misused. The main difference between the two is as follows:
- this
cannot be used in static member functions,
selfcan;
for static member functions /For variable access, it is recommended to use - self
instead of
$this::or
$this->;
is not To access static member variables, - self
cannot be used, only
this;
- this
must be used when the object has been instantiated. ,
selfdoes not have this restriction;
is used within a non-static member function, - self
suppresses polymorphic behavior and refers to the function of the current class; and
thisReference the override function of the calling class (if any). The purpose of
self
After reading the differences between the above three keywords, is the purpose of self immediately apparent? ? To sum up in one sentence, that is:
self always points to "the current class (and class instance)". The details are:
- Replace the class name, refer to the static member variables and static functions of the current class;
- Suppress polymorphic behavior, refer to the functions of the current class instead of the overridden implementation in the subclass;
groove point
- Among these keywords, only
this
needs to be added with the$
symbol and must be added. Obsessive-compulsive disorder means it is very uncomfortable. ; - Non-static member functions cannot be called through
$this->
in static member functions, but they can be called throughself::
and are not included in the calling function. It can still run smoothly when using$this->
. This behavior seems to behave differently in different PHP versions. It is ok in the current 7.3; - is output in static functions and non-static functions
self
. Guess what the result is? Both arestring(4) "self"
, confusing output; -
return $this instanceof static::class;
There will be syntax errors, but the following two The normal way to write it is:
$class = static::class;
return $this instanceof $class;
// Or like this:
return $this instanceof static;
[Related recommendations: laravel video tutorial]
The above is the detailed content of What is the usage of self in laravel. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Database operations in PHP are simplified using ORM, which maps objects into relational databases. EloquentORM in Laravel allows you to interact with the database using object-oriented syntax. You can use ORM by defining model classes, using Eloquent methods, or building a blog system in practice.

PHP unit testing tool analysis: PHPUnit: suitable for large projects, provides comprehensive functionality and is easy to install, but may be verbose and slow. PHPUnitWrapper: suitable for small projects, easy to use, optimized for Lumen/Laravel, but has limited functionality, does not provide code coverage analysis, and has limited community support.

The latest versions of Laravel 9 and CodeIgniter 4 provide updated features and improvements. Laravel9 adopts MVC architecture and provides functions such as database migration, authentication and template engine. CodeIgniter4 uses HMVC architecture to provide routing, ORM and caching. In terms of performance, Laravel9's service provider-based design pattern and CodeIgniter4's lightweight framework give it excellent performance. In practical applications, Laravel9 is suitable for complex projects that require flexibility and powerful functions, while CodeIgniter4 is suitable for rapid development and small applications.

Laravel - Artisan Commands - Laravel 5.7 comes with new way of treating and testing new commands. It includes a new feature of testing artisan commands and the demonstration is mentioned below ?

Compare the data processing capabilities of Laravel and CodeIgniter: ORM: Laravel uses EloquentORM, which provides class-object relational mapping, while CodeIgniter uses ActiveRecord to represent the database model as a subclass of PHP classes. Query builder: Laravel has a flexible chained query API, while CodeIgniter’s query builder is simpler and array-based. Data validation: Laravel provides a Validator class that supports custom validation rules, while CodeIgniter has less built-in validation functions and requires manual coding of custom rules. Practical case: User registration example shows Lar

When choosing a framework for large projects, Laravel and CodeIgniter each have their own advantages. Laravel is designed for enterprise-level applications, offering modular design, dependency injection, and a powerful feature set. CodeIgniter is a lightweight framework more suitable for small to medium-sized projects, emphasizing speed and ease of use. For large projects with complex requirements and a large number of users, Laravel's power and scalability are more suitable. For simple projects or situations with limited resources, CodeIgniter's lightweight and rapid development capabilities are more ideal.

For beginners, CodeIgniter has a gentler learning curve and fewer features, but covers basic needs. Laravel offers a wider feature set but has a slightly steeper learning curve. In terms of performance, both Laravel and CodeIgniter perform well. Laravel has more extensive documentation and active community support, while CodeIgniter is simpler, lightweight, and has strong security features. In the practical case of building a blogging application, Laravel's EloquentORM simplifies data manipulation, while CodeIgniter requires more manual configuration.

PHP Unit and Integration Testing Guide Unit Testing: Focus on a single unit of code or function and use PHPUnit to create test case classes for verification. Integration testing: Pay attention to how multiple code units work together, and use PHPUnit's setUp() and tearDown() methods to set up and clean up the test environment. Practical case: Use PHPUnit to perform unit and integration testing in Laravel applications, including creating databases, starting servers, and writing test code.
