C++23 Update We now finally have std::print as a way to use std::format for output directly: #include <print> #include <string> int main() { // … std::print(“Follow this command: {}”, myString); // … } This combines the best of both approaches. Original Answer It’s compiling because printf isn’t type safe, since it uses variable arguments in … Read more
Secret API objects reside in a namespace. They can only be referenced by pods in that same namespace. Basically, you will have to create the secret for every namespace. For more details, see this: Kubernetes Documentation / Concepts / Configuration / Secrets
Short answer: use XPath local-name(). Like this: xPathFactory.newXPath().compile(“//*[local-name()=’requestURL’]/text()”); will return /CAMERA/Streaming/status Or you can implement a NamespaceContext that maps namespaces names and URIs and set it on the XPath object before querying. Take a look at this blog article, Update: the article is down, you can see it on webarchive Solution 1 sample: XPath xpath … Read more
Consider this program: line# 1 #include <string> 2 3 using namespace std; 4 5 struct string { const char* p; }; // Beware: another string! 6 7 int main() 8 { 9 string x; // Error: ambiguous – which string is wanted? 10 } If you try to compile it, you’ll see errors: g++ using.cc … Read more
Assuming you’ve already tried to force-delete resources like: Pods stuck at terminating status, and your at your wits’ end trying to recover the namespace… You can force-delete the namespace (perhaps leaving dangling resources): ( NAMESPACE=your-rogue-namespace kubectl proxy & kubectl get namespace $NAMESPACE -o json |jq ‘.spec = {“finalizers”:[]}’ >temp.json curl -k -H “Content-Type: application/json” -X … Read more
Consider two libraries called Foo and Bar: using namespace foo; using namespace bar; Everything works fine, and you can call Blah() from Foo and Quux() from Bar without problems. But one day you upgrade to a new version of Foo 2.0, which now offers a function called Quux(). Now you’ve got a conflict: Both Foo … Read more
They cover completely different use cases. CSS namespaces are for applying CSS to XML documents that mix elements from different XML namespaces. e.g. so you can target <foo:p> and <bar:p> without confusion. SMACSS covers techniques for writing robust CSS that doesn’t interfere with other parts of the page. e.g. so that .title in your address … Read more
No, it’s not possible befriend a namespace. If nothing else, it would constitute a “security breach,” as namespaces can be extended anywhere. So anyone could add an arbitrary function to the namespace and access the class’s non-public data. The closest you can get is the solution you propose, making those functions static members of a … Read more
Is there a god (i.e. a parent) object? Yes. More technically, it’s the global object that all these primitives are members of; it just happens that in the browser, the window object is the global object. > window.String === String; true Why is it bad idea to have vars/functions on a global level? Because if … Read more