Community Page
- www.wp-fun.co.uk Jump to website »
-
Subscribe -
Community
-
Top Commenters
-
Popular Threads
-
Recent Comments
- Hi there Andrew. your "Fun with Categories" plugin is certainly a very useful plugin. But I am having a little bit of trouble and was wondering if there is any example templates out...
- Great post! I've bookmarked your blog. Hope we can swap links. Why can't I open your rss feed? No post is showing. Best Regards! Ginj
- Can you paste the entire error in?
- I'm getting the Parse error: syntax error, unexpected T_STRING, expecting '(' in error too.
- Atompub is really available or not? But i think this project will be more useful for the normal people to understand..Always Google rocks and leave their marks in every field..
Jump to original thread »
I think you should give objects a try, for more reasons than just avoiding naming collisions. Here’s why.
I think I’m a pretty typical Wordpress user. I learned a lot of my PHP by playing with themes to get them to do things they didn’t by default. So when I d ... Continue reading »
I think I’m a pretty typical Wordpress user. I learned a lot of my PHP by playing with themes to get them to do things they didn’t by default. So when I d ... Continue reading »
1 year ago
ie.
class myClass(){
function __construct(){
// do something
}
function myClass($args){
//php 4 compliant fake constructor
$args = func_get_args();
call_user_func_array(array(&$this, '__construct'), $args);
}
1 year ago
Is there a benefit to using call_user_function over simply calling myClass from within the __construct method?
1 year ago
But I don't know if there are some valid reasons to not use __contruct($args) { $this->myClass($args) ); as you suggest.
Btw, I've studied a little more and I've discovered that
however, IMHO, this should not be used. Especially if you work with object that extends other object. Because it should be very easy to break your code simply changing the name of the parent class [parent::MyParent ==> parent::NewParentName ].
1 year ago
I guess it really is a case of deciding how long the plugin is likely to be around, and whether you want to support it later in its life to upgrade to PHP 6.
Having said that many hosts are only now getting up to PHP 5. If PHP 6 won't be backward compatible then I guess you need to wonder how long it will really be until PHP 6 is offered. We could be facing up to 5 years before it becomes well supported.
That's a long time for a plugin.
1 year ago
That caveat aside, this is a nice little site you've got here. I'll subscribe once you change the title ;-)
Keep up the good work.
1 year ago
1 year ago
Class wp_something {
...
}
new wp_something;
because, actually, I only need to run the constructor of the class - I do not need a variable storing the created object ;)