PHP Namespaces in Under 5 Minutes

So nice, thanks Troy :)

Hey Aina,

This course has only a single video that is completely free: https://symfonycasts.com/screencast/php-namespaces/namespaces - Could you tell us more about what exactly does not work for you? Could you try again, please? Or try to open that video in Chrome Incognito mode? I believe that was a temporary network issue, so it should work for you now unless you have some restrictions to Vimeo videos in your country since all our videos are hosted there.

Cheers!

Hey Adam,

My apologies for the inconvenience, I think you're right about the cache because the challenge it's working for me. You can wait like 15 minutes to let the cache refresh and try again.
Please, let me know if the problem persists.

Hi!

yep, that was a cache problem :) Now it's works fine. Thanks!

Hey, thank you!

Hey Jeric,

We're glad you like it! Honestly, this is my favorite tutorial :p

Cheers!

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

Cheers!

Hey R0bertinski!

I wonder if (English) sub-titles would help? I want to do the most useful thing for our non-native English-speaking friends :).

Thanks!

Yes, It would help :D

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).

Hi there!

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.

Cheers!

120 seconds + this explanation and I'm ready to go =)
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 :)

Hi there!

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.

Cheers!