>>But the built-in types are not identifiers, they're keywords.
If I ever make a programming language, I'll be sure to eliminate the distinction
>>Now you're starting to word your explanations like I do, and that's frightening.
At least I'm learning something from your explanations
>>Even more confusingly, a namespace is a name space, but a name space is not necessarily a namespace.
And yet, a namespace isn't one of the four name spaces?
So there's name space (abstract), four name spaces (language-defined), and any number of namespaces (user-defined), and all three are distinct concepts although interconnected in a fundamental sort of way. Got it
Prelude, you have an indescribable way of getting your point across in the most confusing manner possible.
**EDIT**
Just some housekeeping details:
-name spaces and namespaces are both examples of name spaces.
-->There is no naming conflict here because one 'name space' is in the (abstract) name space and one is in the (language-defined) name space
-in Prelude's code example, main() didn't return a value