Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
What is "protected static?"
If I were to explain what a property was in OOP and then go on to explain a constructor, I would ask my audience to envision a spreadsheet. A property is like a column. It's just a digital placeholder. A constructor assigns a value to that column.
"Visibility" is all about how accessible those properties in the context of your app. Public means that it's available throughout your entire online community. "Protected" means that it's only available within the Class that it was instantiated along with any Classes it might be associated with (parent / child). "Private" means that it's only available within the Class it was created in.
"Protected Static." I get the "protected" part and I've attempted to google "static," but I'm still a little fuzzy.
From what I can gather, making a Property "static" eliminates the need for it to be instantiated using the $this (pseudo variable which means "this current object"). Frankly, I've never used that, but I want to understand it. Here's the code I'm attempting to deconstruct:
What is $debug=false? It's not referenced anywhere else on the page and I cannot figure out it's purpose or why it would be assigned a "protected static" dynamic.
Please raise your hand if you know the answer :)...
"Visibility" is all about how accessible those properties in the context of your app. Public means that it's available throughout your entire online community. "Protected" means that it's only available within the Class that it was instantiated along with any Classes it might be associated with (parent / child). "Private" means that it's only available within the Class it was created in.
"Protected Static." I get the "protected" part and I've attempted to google "static," but I'm still a little fuzzy.
From what I can gather, making a Property "static" eliminates the need for it to be instantiated using the $this (pseudo variable which means "this current object"). Frankly, I've never used that, but I want to understand it. Here's the code I'm attempting to deconstruct:
class StatementImage {
protected $statementid;
protected $pipe_delim;
protected $statement_data;
protected static $debug = false;
/**
* Takes the pipe delimited file and creates a statementimage entity.
*/
public function __construct($pipe_delim) {
$this->pipe_delim = $pipe_delim;
$this->statement_data = StatementImage::pipeToArray($pipe_delim);
$this->statementid = str_replace('T', '', $this->statement_data['statement']['statement_pin']);
}
What is $debug=false? It's not referenced anywhere else on the page and I cannot figure out it's purpose or why it would be assigned a "protected static" dynamic.
Please raise your hand if you know the answer :)...
Asked:
4-
2
4 Solutions
LVL 44
Static properties are not associated with a particular instance. In other words, all StatementImages will have $debug = false, while StatementImage A could have a different $statementid than StatementImage B.
And you're correct, $debug is not being referred to in the code you posted. Perhaps it's referenced somewhere else? Or maybe it was created for debugging but the related code has been removed ?
I get it...
So, anytime you include a static property within a class, every function within that class will AUTOMATICALLY have that property attached to it.
So, in this instance, instead of having to repeatedly assign a "false" value to the $debug property (although we don't know where that puppy is right now), because it's "static," it's present throughout by default, yes?
Thanks!
So, anytime you include a static property within a class, every function within that class will AUTOMATICALLY have that property attached to it.
So, in this instance, instead of having to repeatedly assign a "false" value to the $debug property (although we don't know where that puppy is right now), because it's "static," it's present throughout by default, yes?
Thanks!
Correct. Sort of. You could have a dynamic / non-static property that's assigned a value in the constructor. So you would have the same value for the property across all instances of the class when they are first instantiated, and you wouldn't have to "assign" the value to the property because it's handled in the constructor.
Perhaps this will help clarify the difference. Consider the implications of the following aspect of static properties: there is only one copy of a static property and it's shared among all instances of the class. You can change it... but it changes for all instances.
Perhaps this will help clarify the difference. Consider the implications of the following aspect of static properties: there is only one copy of a static property and it's shared among all instances of the class. You can change it... but it changes for all instances.
You're right! I get what you're saying about the dynamic, non-static property scenario in the constructor - that would work. So, conceivably there are two different ways in which the guy who originally wrote this code could've done what he was striving to accomplish with the "protected static $debug=false" code.
He could've used:
protected static $debug=false
OR
He could've done something like:
protected $debug
public function __construct {
$this->debug=false;
}
Yeah?
He could've used:
protected static $debug=false
OR
He could've done something like:
protected $debug
public function __construct {
$this->debug=false;
}
Yeah?
If that approached were used, each instance of StatementImage would have its "own" debug property. That means if you instantiated a new instance, debug would be false, you could change it to true in that instance, but all of the other StatementImage objects would have debug = false.
But yes, you can set the value in the constructor like that, and then that property is assigned a value when the instance is instantiated.
But yes, you can set the value in the constructor like that, and then that property is assigned a value when the instance is instantiated.
When I think of static properties and methods, I think that "static" is an overloaded term.
http://php.net/manual/en/language.oop5.static.php
In addition to late static bindings, you can get access to static properties and methods without creating an object instance from the class. Thus the class method can act as a "helper function" for other programming. In the case of a protected static method. the class method can act as a helper function for this class and extensions of class, but it cannot refer to $this, nor can it be a helper function for programming that is outside the inheritance chain.
http://php.net/manual/en/language.oop5.static.php
In addition to late static bindings, you can get access to static properties and methods without creating an object instance from the class. Thus the class method can act as a "helper function" for other programming. In the case of a protected static method. the class method can act as a helper function for this class and extensions of class, but it cannot refer to $this, nor can it be a helper function for programming that is outside the inheritance chain.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now