concept

So, I had an argument with my professor earlier defending that NULL is not a pointer, but he kept on insisting that it is because there is such a thing as NULL pointer. So, here I am now a little bit confused if NULL is really a pointer or not I already tried search over the internet but couldn't find any answer, so my last resort is here In C, NULL is a macro that expands to a null pointer constant. 7.19p3 The macros are NULL which expands to an implementation-defined null pointer constant; ... A null pointer constant is an integer constant expression with the value 0 ( e.g., 0 , 1-1 , 42*0LL

The question I asked might be closed, But i just want to know that is it necessary to write else part of every if condition. One of my senior programmer said me that "you should write else part in every if condition" . Suppose we have no condition for write in else part then what should we do ? I assume a healthy discussion will going on here.... That's a horrible idea. You end up with code of the form: if (something) { doSomething(); } else { } How anyone could think that's more readable or maintainable that not having an else at all is beyond me. It sounds like one of those rules made up by

Looking at the possible implementation of the same_as concept at https://en.cppreference.com/w/cpp/concepts/same_as i noticed something strange is happening. namespace detail { template< class T, class U > concept SameHelper = std::is_same_v<T, U>; } template< class T, class U > concept same_as = detail::SameHelper<T, U> && detail::SameHelper<U, T>; The first question is why a SameHelper concept is nedded? The second is why same_as checks if T is the same as U and U the same as T ? Isn't it redundant? Interesting question. I have recently watched Andrew Sutton's talk on Concepts, and in the Q

I want to know the process which usually web apps follow to maintain login between multiple requests and also how they manage things using COOKIES. In my login form I am providing "Remember Me" feature. When user login then I check the username and password validity from database. If its valid then I check if "Remember me" is selected, if yes then storing username and password in session, encrypted format. And finally storing username and password in SESSION. When user navigates form one page to another, first I run login check script which checks if there is any value in cookies, then it

In the python tutorial it's said that " Python supports a limited form of multiple inheritance ". What are the limitations? Apart from @Matt Anderson's answer I think that the limitations is in fact for the old style classes (which the tutorial for Python 2.6 still addresses ). In the Python 3 tutorial the text is now: Python supports a form of multiple inheritance as well . I'm not sure to what limitations the author of the python tutorial was referring, but I would guess it has in part to do with the way that method / attribute lookup is implemented in python (the "method resolution order"

After playing around with Vaadin for about a week I'm curious about how Vaadin uses GWT. GWT compiles Javacode to Javascript. This has to be done everytime when you are redeploying. Since Vaadin has to be understood as a server-centric framework, eliminating your flexibility on writing Code that is executed on Clientside and moving everything to the server (which sounds worse than it actually is), the GWT Compiler only runs once a time. For example this happens when you are importing a plugin from the vaadin website. But it can't be that easy right? If it only would compile the code of the