Still not quite comfortable with PHP 5.3 namespaces? No problem! Give us
120 seconds and we'll introduce you to all the crazy characters ("namespace",
"use" and "\") and show you how they work.
Ah, sorry I misunderstood you. I'm glad you discovered the answer :)
Hey, thanks for your reply. However, I meant just the beginning of the file, when you declare to 'use' a class from another, non-global namespace. I found the answer somewhere else, turns out that it doesn't make any difference, but it should be written without the backslash (as a convention). Cheers!
Hey Dan Marshall
If you prepend a backslash when instantiating an object, i.e. $movie = new \Movie() then, PHP will try to find that class from the global scope (The global scope is where built-in classes live, like for example $today = new \DateTime())
$movie = new \Movie()
$today = new \DateTime()
I hope it helps. Cheers!
Thanks for the tutorial, great! Could you elaborate on the backslashes, though? Should it be 'use \...' or 'use ...' from inside a namespace?
Thanks, kept your 120 second promise :)
Glad you liked this tutorial! And thanks for your feedback :)
Very clear! Thank you very much for that tutorial! :) <3
easy, fast and great !!!!Thanks
We're glad you like it! Honestly, this is my favorite tutorial :p
Sweet As! Thank you!
Hey Mr TK
In this case we are using "require" in a file (some-other-file.php) that doesn't define a namespace, the one who has a namespace is the Foo class, so if you want to create a Foo object in other file, you have two options
1) In that file, define it's namespace and write a "use" statement that points to the "Foo" class
2) Don't define a namespace and use "require" or "include" that points for that class
And why do you need to require a file when namespacing? Isn't namespacing intended to do away with requiring?
Awesome! Really save my time!
It think it would actually help !I generally have the same 'problem'.But not putting sub-titles also makes us focusing more on the screen and the intonation of the voice.
So having the choice of activating sub-titles would be a benefit (in my opinion).
Waow ! These 2 minutes were incredibly efficient (in my case).Thank you for this course, I feel like I've just discovered my new Bible with knpuniversity :)
Hey, thank you!
The best php namespace tutorial.... Great... keep it up...
excellent explanation. Thanks!!!
Wish documentation was like this.
120 seconds + this explanation and I'm ready to go =)Thank you!
guess i'm not the first, who say that this titorial is great! Thank you!
Ha, 120 seconds is definitely a rush! You can't slow down the video yet, but we're adding speed control really soon :)
Quite helpful, many thanks! I realized it before I know I realized it (does that make sense? :P) But do you happen to have a 0.75x speed playback option? 120 seconds sound like a rush to me~~ :-D
great explanation, thanks :)i get it now!
I got myself ready to sit down and read/watch for several minutes on how to properly use namespaces in PHP. I appreciate how easy this tutorial was to follow.
useful tip :-) Thank you.
Yes, It would help :D
Very nice tutorial
I wonder if (English) sub-titles would help? I want to do the most useful thing for our non-native English-speaking friends :).
I am used to listen videos in english, but is very complicate to understand this videos, because she speak very fast.
So nice, thanks Troy :)
Brilliant. I just wasted my time reading two different tutorials on namespaces and still didn't understand it. Watched your video and got it immediately. Thanks Leanna and Ryan for uncomplicating this subject.
Great overview. Only thing I think it could use is to mention that the main use of namespaces is to stop method names conflicting. Aside from that great job!
Actually, namespaces and autoloading are 2 separate things, though in practice, due to PSR-0 autoloaders, they are quite related.
Namespaces are all about basically making class names really long, and then giving us a "use" statement to help shorten things. On its own, it doesn't help with removing the require/include statements. So you're right, on their own, namespaces actually *add* code and make things longer. Really, namespaces weren't created for you and I, they were created for library authors to avoid name collisions (like you mentioned). For us, they just make things longer :).
But in practice (and you're totally right about this part), if you use namespaces properly, AND you use a PSR-0/PSR-4 autoloader (like the one provided in Composer), then you'll be able to remove your require/include statements. The autoloader basically leverages namespaces to do this, but namespaces on their own don't allow you to remove those ugly require/include things from your code.
I hope that clarifies - it's confusing because namespaces *seem* to make include/require statements no longer necessary (because in practice, this is true). But in reality, on their own, they just make class names longer and mean more typing.
So, why wasn't the required_once function removed from your example? If that function is required to import your classes, then there is no purpose in updating code to include namespaces, since there is no benefit in reducing code, instead, you've increase code.
The purpose of adding a namespace, not only has to reduce class name clashes, but also automate the finding and binding of classes somehow, otherwise there is no use to using namespaces.
That was awesome. Thanks for this. Namespaces and object-oriented code in PHP are bringing me back.
Namespaces and using the include/require statements don't do the same thing - it's one of the trickiest parts of learning namespaces. You still need to include/require any file before using the class inside of it (unless you use an autoloader, like the one Composer gives you). Namespaces have nothing to do with that part.
The point of namespaces is, basically, to give you a systematic way to make your class names longer. When you have the `Acme\Tools` namespace, the full class name ends up being `Acme\Tools\Foo`. Why is this useful? Well, on its own, it's not :). It's really so that 2 3rd-party library authors an choose 2 different namespaces so that their class names don't conflict. Namespaces really help to serve that purpose: to avoid conflicts between libraries.
If you want to see a little bit more on the autoloading side of things (i.e. removing the need for require/include) - check out http://knpuniversity.com/sc.... Again, it's actually unrelated to namespaces.
You explained what namespaces do, but you didn't explain why I might need them. You say "This is just like referring to a file by its absolute path.", so ... why don't you just do that?
Wow... you really did it in 120 secs :-)