First – you don’t need a navigator; SelectNodes / SelectSingleNode should suffice. You may, however, need a namespace-manager – for example: XmlElement el = …; //TODO XmlNamespaceManager nsmgr = new XmlNamespaceManager( el.OwnerDocument.NameTable); nsmgr.AddNamespace(“x”, el.OwnerDocument.DocumentElement.NamespaceURI); var nodes = el.SelectNodes(@”/x:outerelement/x:innerelement”, nsmgr);
Your guess as to the intent of || {} is pretty close. This particular pattern when seen at the top of files is used to create a namespace, i.e. a named object under which functions and variables can be created without unduly polluting the global object. The reason why it’s used is so that if … Read more
You should definitely NOT use using namespace in headers for precisely the reason you say, that it can unexpectedly change the meaning of code in any other files that include that header. There’s no way to undo a using namespace which is another reason it’s so dangerous. I typically just use grep or the like … Read more
You need to declare the namespace in your XSLT, and use it in XPath expressions. E.g.: <xsl:stylesheet … xmlns:my=”http://www.mysite.com”> <xsl:template match=”/my:MyRoot”> … </xsl:template> </xsl:stylesheet> Note that you must provide some prefix if you want to refer to elements from that namespace in XPath. While you can just do xmlns=”…” without the prefix, and it will … Read more
Linked to, but not explicitly mentioned here, is exactly when __all__ is used. It is a list of strings defining what symbols in a module will be exported when from <module> import * is used on the module. For example, the following code in a foo.py explicitly exports the symbols bar and baz: __all__ = … Read more
I use the approach found on the Enterprise jQuery site: Here is their example showing how to declare private & public properties and functions. Everything is done as a self-executing anonymous function. (function( skillet, $, undefined ) { //Private Property var isHot = true; //Public Property skillet.ingredient = “Bacon Strips”; //Public Method skillet.fry = function() … Read more
There is actually a (subtle) difference between the two. Imagine you have the following code in File1.cs: // File1.cs using System; namespace Outer.Inner { class Foo { static void Bar() { double d = Math.PI; } } } Now imagine that someone adds another file (File2.cs) to the project that looks like this: // File2.cs … Read more
Why is “using namespace std;” considered bad practice?
You can use forward declaration of your class second and use a pointer. Only the implementation must know the declaration of your class Second. namespace A { class Second; // Forward declaration class First { public: First(); ~First(); private: Second* s; // Pointer on a forward class }; class Second { private: First f; }; … Read more
Short Answer It’s boilerplate code that protects users from accidentally invoking the script when they didn’t intend to. Here are some common problems when the guard is omitted from a script: If you import the guardless script in another script (e.g. import my_script_without_a_name_eq_main_guard), then the second script will trigger the first to run at import … Read more