首先,我定义个类,实现单例模式:(这里是简单一写,就是个最基本的单例)
<code>class Demo { public static $instance; private function __Construct() { //TODO } public static function getInstance() { if(!self::$instance){ self::$instance = new static(); } return self::$instance; } public function call() { //其他方法 } }</code>
下面有两种方式实例化类:
1.在需要用的地方
<code>$aa = Demo::getInstance(); $bb = Demo::getInstance(); $cc = Demo::getInstance();</code>
这样调用肯定是没问题的,一般情况也是这样初始化。
2.定义一个普通类,写个函数初始化,保存在一个静态变量,如下:
类:
<code>class Demo{ public function __Construct(){ //TODO } }</code>
函数:
<code>function get_obj(){ static $obj; if($obj){ return $obj; }else{ $obj = new Demo; return $obj; } }</code>
在需要调用的地方这样写:
<code>$obj = get_obj(); $obj->call(); $obj2 = get_obj(); $obj2->call(); $obj3 = get_obj(); $obj3 = get_obj();</code>
这样不是也只实例化一次这个类吗?
回复内容:
首先,我定义个类,实现单例模式:(这里是简单一写,就是个最基本的单例)
<code>class Demo { public static $instance; private function __Construct() { //TODO } public static function getInstance() { if(!self::$instance){ self::$instance = new static(); } return self::$instance; } public function call() { //其他方法 } }</code>
下面有两种方式实例化类:
1.在需要用的地方
<code>$aa = Demo::getInstance(); $bb = Demo::getInstance(); $cc = Demo::getInstance();</code>
这样调用肯定是没问题的,一般情况也是这样初始化。
2.定义一个普通类,写个函数初始化,保存在一个静态变量,如下:
类:
<code>class Demo{ public function __Construct(){ //TODO } }</code>
函数:
<code>function get_obj(){ static $obj; if($obj){ return $obj; }else{ $obj = new Demo; return $obj; } }</code>
在需要调用的地方这样写:
<code>$obj = get_obj(); $obj->call(); $obj2 = get_obj(); $obj2->call(); $obj3 = get_obj(); $obj3 = get_obj();</code>
这样不是也只实例化一次这个类吗?
完善的单例应该是这样的
class Foobar { static private $instance; // 禁止外部new Foobar private function __construct() { } // 禁止clone $foobar private function __clone() { } static public function getInstance() { retrun self::$instance ?: (self::$instance = new self); } }
如果还要考虑到继承的话
class Foo { static private $instances = []; protected function __construct() { } final private function __clone() { } final static public function getInstance() { $class = get_called_class(); if (!isset(self::$instances[$class])) { self::$instances[$class] = new static; } return self::$instances[$class]; } } class Bar extends Foo { } $foo = Foo::getInstance(); $bar = Bar::getInstance();
get_obj()那种写法,也可以达到目的,但无法禁止new和clone,也就无法做到真正的单例
这问题我也有印象,我也答过一次
http://segmentfault.com/q/1010000003894638
看了一下还是题主你,为毛要问两遍……
然后你的第二种方式并非单例,请不要陷入抠概念的误区
偶尔也有你这种用法的,少见,并且不好。在一般情况下用一个特定对象就行了,特殊情况下需要新的实例的场合会用,但一般也不会这么写(早期的PHP会有一些类这么做)
= = 所以呢?
两种写法而已啊。。。
另外,你无论怎么看,都还是第一种更清晰,更独立,更好用啊。。。
第一种封装、抽象的更好,更加符合面向对象啊。
存一个静态变量或者另外弄个函数什么的,你不觉得乱嘛。。。
静态变量可以定义在函数里或者类属性,两种写法都可以,但前者封装性会比较好些。
楼主给了我启发,过程式编程中,在全局函数内用静态变量存储数据库连接实现单例:
<code><?php // config.php $app = array( 'db_host' => '127.0.0.1', 'db_username' => 'root', 'db_password' => '', 'db_name' => 'mysql' ); // functions.php function cn_db() { global $app; static $mysqli; if ($mysqli) { return $mysqli; } else { $mysqli = new mysqli($app['db_host'], $app['db_username'], $app['db_password'], $app['db_name']); return $mysqli; } } function cn_foo1() { $mysqli = cn_db(); return $mysqli->query('select user,host from user where user = \'root\'')->fetch_all(); } function cn_foo2() { $mysqli = cn_db(); return $mysqli->query('select user,host from user')->fetch_all(); } // controller + view print_r(cn_foo1()); print_r(cn_foo2());</code>
$instance = new static(); (楼主这行代码写错了),感觉单例模式就是个思想,你第一个例子就是面向对象,第二个例子既有面向对象,又有面向过程。
单例模式是指整个应用中类只有一个对象实例的设计模式。
第二种方式是单例吗?
<code>class Demo { public function __construct(){ //TODO } } function get_obj() { static $obj; if($obj){ return $obj; }else{ $obj = new Demo; return $obj; } } var_dump(get_obj()); var_dump(new Demo); </code>
得出的是2个不同的实例
你那样写不符合面向对象思想的,而且你的单例模式也不完整,没有考虑到clone和extends的情况。可以参考下http://www.xtwind.com/design-pattern-singleton.html
单例模式,是一种设计思想实现方式
单例首先是面向对象里面的概念,
第二种就不是面向对象
get_obj()那种写法无法保证外部不new Demo对象
单例的要义第一:私有化构造方法,当然PHP还提供了clone魔术方法,也要私有化。这样做事为了保证外部实例化对象的入口只有一个,只能是我们暴露出来的静态函数getInstance()
单例模式,三私一公,其中的三私:构造方法,克隆魔术方法,实例化对象。一公:对外提供的方法

ThebestapproachforsendingemailsinPHPisusingthePHPMailerlibraryduetoitsreliability,featurerichness,andeaseofuse.PHPMailersupportsSMTP,providesdetailederrorhandling,allowssendingHTMLandplaintextemails,supportsattachments,andenhancessecurity.Foroptimalu

The reason for using Dependency Injection (DI) is that it promotes loose coupling, testability, and maintainability of the code. 1) Use constructor to inject dependencies, 2) Avoid using service locators, 3) Use dependency injection containers to manage dependencies, 4) Improve testability through injecting dependencies, 5) Avoid over-injection dependencies, 6) Consider the impact of DI on performance.

PHPperformancetuningiscrucialbecauseitenhancesspeedandefficiency,whicharevitalforwebapplications.1)CachingwithAPCureducesdatabaseloadandimprovesresponsetimes.2)Optimizingdatabasequeriesbyselectingnecessarycolumnsandusingindexingspeedsupdataretrieval.

ThebestpracticesforsendingemailssecurelyinPHPinclude:1)UsingsecureconfigurationswithSMTPandSTARTTLSencryption,2)Validatingandsanitizinginputstopreventinjectionattacks,3)EncryptingsensitivedatawithinemailsusingOpenSSL,4)Properlyhandlingemailheaderstoa

TooptimizePHPapplicationsforperformance,usecaching,databaseoptimization,opcodecaching,andserverconfiguration.1)ImplementcachingwithAPCutoreducedatafetchtimes.2)Optimizedatabasesbyindexing,balancingreadandwriteoperations.3)EnableOPcachetoavoidrecompil

DependencyinjectioninPHPisadesignpatternthatenhancesflexibility,testability,andmaintainabilitybyprovidingexternaldependenciestoclasses.Itallowsforloosecoupling,easiertestingthroughmocking,andmodulardesign,butrequirescarefulstructuringtoavoidover-inje

PHP performance optimization can be achieved through the following steps: 1) use require_once or include_once on the top of the script to reduce the number of file loads; 2) use preprocessing statements and batch processing to reduce the number of database queries; 3) configure OPcache for opcode cache; 4) enable and configure PHP-FPM optimization process management; 5) use CDN to distribute static resources; 6) use Xdebug or Blackfire for code performance analysis; 7) select efficient data structures such as arrays; 8) write modular code for optimization execution.

OpcodecachingsignificantlyimprovesPHPperformancebycachingcompiledcode,reducingserverloadandresponsetimes.1)ItstorescompiledPHPcodeinmemory,bypassingparsingandcompiling.2)UseOPcachebysettingparametersinphp.ini,likememoryconsumptionandscriptlimits.3)Ad


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

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

SublimeText3 English version
Recommended: Win version, supports code prompts!

SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

Dreamweaver Mac version
Visual web development tools

WebStorm Mac version
Useful JavaScript development tools
