Avoiding conflicts using namespaces
When writing code, you will constantly name things. The problem is, what if you give something a name that is already being used? We now know that the code for an application can consist of thousands of lines of code divided into hundreds of files. How can you make sure that the names you give something are not already taken? We also learned that we can install packages with code that others have written. How can we make sure that they have not given their packages names that we have already used? Or how can we make sure that a package we install is not using names that another package we already installed is using?
As you can see, handling names can be tricky. Let's look at an example. In Chapter 8, Understanding Functions, we will discuss what a function is and how it works. For this example, all we need to know about functions is that they have a name and consist of several lines of code. We use the function name to call it, which will...
