Tips
In order to write future-proof code, it is recommended that you prefix (or suffix) anything that goes into the global namespace with an uncommon 3-4 letter prefix (or suffix) separated with an underscore. It is recommended that in order to prevent namespace clashes with other userland code that projects research existing prefixes (or suffixes) used in other projects and advertise their chosen prefix (or suffix) appropriately. Examples:
MyPx_someFunc()
Foo_Date
$asdf_dbh
Коментарии
I don't think it makes sense nowadays. We have namespaces now!@willian at gt44 dot com: What about clashes of the namespace? It is still good advice to check for previously used names before assigning anything to the global namespace.The javascript community has developed a strong cultural bias against adding anything to the global namespace. (See e.g. Addy Osmani's article on Essential JavaScript Namespacing Patterns .) Namespaces have been available in JS for many years and are ubiquitous. There is also a great deal of freely available tutorial material for the interested reader.Even though nowadays we do have namespaces, for the cases in which the user chooses to not use namespaces theses tips should be followed.