TSQL Can be done on stack overflow?

http://data.stackexchange.com/stackoverflow/query/edit/483660 This will make learning T-SQL easier.

Having trouble invoking static methods in VB.net

Static Methods. AKA: "shared" in vb.net termonology.
Here is the paste bin: http://pastebin.com/RC9p74sE

Update: I was being stupid. The static methods were throwing an error because I was writing the statements within the class, but NOT within a function.
Fix here:http://pastebin.com/2MsCzaMm

CodeEval VB.Net Sample Code Bug Fix

On CodeEval.com: Compiler error around this location, the compiler hasn't implemented the error message, nor error recovery, so the compiler will probably crash soon.

Reason:
The sample code for VB.NET has a typo in it.
GetCommandLneArgs should be: 
GetCommandLineArgs 

Module Challenge
    Sub Main()
        Dim test As String
        Using fileStream As New System.IO.StreamReader(System.Environment.GetCommandLneArgs()(1))
            Do Until fileStream.EndOfStream
                test = fileStream.ReadLine
               'test' represents the test case, do something with it
               ...
               ...
            Loop
        End Using
    End Sub
End Module

Entity Data Model Wizard Shortcut

Can't seem to find the shortcut mapping command for: "Entity Data Model Wizard" within visual studio. I wish there was some type of "Echo all commands" in visual studio like there is in 3DSMax. Then I could see what commands were issued to open what windows. Tried getting the actual class of the window using Auto Hot Key. While it gave me some information, none of it that I could use to identify the window I want. Sucks because I know I should be able to wire this window to a hotkey. Once that window is already open though, you have a lot of shortcut options. http://stackoverflow.com/questions/23528347/keyboard-shortcuts-in-edmx-designer

Get Class Of Active Window AHK

So, I was reading all through the documentation looking for a:
WinGetActiveClass
Since there is a WinGetTitle
And a WinGetClass


Turns out:
WinGetClass's behavior IS to get the class of the active window.

This sample code will display the class name of the active window
when you press the enter key:

enter::
{
 ;theClass = class of active window.
 WinGetClass, theClass, A
 msgBox %theClass%
} 

Mixin is not Composition.

http://naildrivin5.com/blog/2012/12/19/re-use-in-oo-inheritance.html

Close Properties Panel Shortcut Visual Studio

There is a shortcut for opening the properties panel in visual studio. But there is not a paired shortcut to CLOSE IT! This is really annoying. I have shortcuts to open all of the panels I use in visual studio. But I can't use any shortcuts to close them. I get that, with a mouse, the opening is much slower than the closing... But it would be nice if we could at the very least, close the ACTIVE PANEL with a shortcut. NOT close the active document. I see the shortcuts for that. I can close all documents. I just can't close the explorer, toolbox, and properties panels with a shortcut. Really annoyed.

Close Solution Explorer Shortcut Visual Studio

There is a shortcut for opening the solution explorer. But there is no shortcut for closing it. Very annoying for someone trying to set up hotkeys!

Close ToolBox Visual Studio

There is a shortcut for opening the toolbox, but not for closing it, what gives?

Stood Vector

Stood Vector: How I heard someone pronounce std::vector on the internet. Figured one day someone might hear it, not know what was meant, and try to google it. Now there will be relevant google results.

Delete Character

Having Delete Be FF or 7F is pretty neat. Origins in punch cards where you could punch out all the bits on a given line to delete/ignore that line if it was a mistake. https://en.wikipedia.org/wiki/C0_and_C1_control_codes#Device_Control

Enforce classes have same static method c++

All my classes must have a method called unitTest in DEBUG mode. This is because I don't want my test code in a separate library.

Separation of concerns is nice and all. But I think that separation also makes it more likely that your test library code will decay.

This might be what I need: http://stackoverflow.com/questions/9346076/static-template-functions-in-a-class

Basically, extend from a header-only class that defines no implementation. And have the function within that class be templated.

Something like:

public:
template< typename T>
    static double foo( vector arr );

In the header, without any implementation.

Can you extend from a class with no implementation? I bet you can. Need to look into that.

Maybe I need a "pure virtual function"? https://blogs.msdn.microsoft.com/oldnewthing/20131011-00/?p=2953

But that specifies type... Do I need a "pure virtual template function"? That sounds fancy and over complicated.

Yes, you can. http://stackoverflow.com/questions/8919566/are-pure-virtual-methods-allowed-within-a-template-class

Ownership of pointers in c++ and borrow boxes

Trying to wrap my head around ownership of pointers in c++. Trying to establish rules to make good software. Here are some ideas. 1. Only one object has ownership of any given object. 2. If an object owns another object, when delete[] is called on the parent, it should be called on the child. 3. If an object does NOT own another object, when we delete[] the parent, the other object referenced from within the parent should not be deleted. 4. Any object should either OWN every object it references, or NOT-OWN every object it references. This is to simplify it. So we know exactly what needs to be done to children when delete[] is called. 5. Don't give out references to stuff you don't own. If a class does NOT own the object, it should not be allowed to give out a reference to it. The object that wants the reference should go to the source. ANALOGY: I can't give library book to stranger. The stranger needs to go to the library to get the book I have. Not the best analogy. Since the book they get from the library would also be the book I have. Because we are talking about reference types, not value types. 6. What about classes that absolutely must own some things, but not others? Classes that need mixed ownership must have a "borrow box" or "sandbox" or whatever you want to call it. It is an object OWNED by the parent, so it can be deleted by the parent when the parent is deleted. HOWEVER, the "borrow box" container never owns anything inside it. So when it is destroyed, none of it's contents are deleted. Again, with the rule of not giving out things you don't own... Borrow boxes should never be passed around. A borrow box should not simply be a wrapper you wrap individual objects in. So that you can pass the wrapper around. That wouldn't solve the problem. It would just add another step. The borrow boxes should be taylored to each and every individual class that needs one. No other classes should know about the borrow boxes. So why even have them then? Is it simply a formality that makes the code easier to read? Is it simply a way to avoid individually flagging ownership? It seems like a good idea. But I need more time to think about it. Is it worth the extra -> jump every time you need to reference it?

Overload = operator c++

I thought I had it... Now all the sudden I am getting the error: error: conversion from 'uint32_t {aka unsigned int}' to non-scalar type 'deathNote' requested... what did mess up??? Solution here: http://www.tutorialspoint.com/cplusplus/assignment_operators_overloading.htm Though I noticed I am having trouble using it with initialization and assignment all in the same line.

Are structs initialized to zero?

Research says that you shouldn't rely on this. Best to include a parameter-less constructor that zeros out all of the member values. The only downside being that it's not longer a POD type by C standards.

object lifetime of structs c++

I know when you want to return a class instance from a function you need to use the new keyword and assign it to a pointer. Is it the same rule for structs? I want my structs on the stack, not the heap. So I'd like to not mess with pointers. But I am afraid doing:

myStruct getStruct(){
  myStruct val;
  return val;
}

Will the instance of myStruct be killed immediately after leaving the function scope? Turns out, this works with structs. Pretty sure it would not work if it were a class. Also strange is that it seems like... All the members of a struct are initialized? Rather than having whatever random data was there before hand? Or maybe I am just lucky... Might want to explicitly init values by specifying a constructor.

+= operator overloading a struct

Overloading the shorthand addition operator (+=) in c++: Note, this is operator overloading the += operator for a STRUCT. called "deathNote". I follow the constant-class rule for classes. But use lowercase for structs because structs are value-types / primitives. So they should be treated like "int", "float", "char", "string", etc. Which all start with lowercase letters.

deathNote operator_-(const deathNote &a){
    this->apples = a.apples + this->apples;
    this->chocolate = a.chocolate + this->chocolate;
    this->paper = a.paper + this->paper;
    return (*this);
}

operator+ must take zero or one argument

struct deathNote{

uint32_t apples;
uint32_t chocolate;
uint32_t pages;

deathNote operator+(const deathNote &a, const deathNote &b){
   deathNote ret_val;
   ret_val.apples = a.apples + b.apples;
   ret_val.chocolate = a.chocolate + b.chocolate;
   ret_val.pages = a.pages + b.pages;
   return ret_val;
}

};//struct

//ERROR: operator+ must take zero or one argument.
//The fix? One parameter is implied via the "this" pointer.

//WORKING OVERLOADED OPERATOR:
deathNote operator+(const deathNote &a){
   deathNote ret_val;
   ret_val.apples = a.apples +  this -> apples;
   ret_val.chocolate = a.chocolate +   this -> chocolate;
   ret_val.pages = a.pages +   this -> pages;
   return ret_val;
}

Use structs when 16 bytes or under

Source: https://msdn.microsoft.com/en-us/library/ms229017%28v=vs.110%29.aspx
✓ CONSIDER defining a struct instead of a class if instances of the type are small and commonly short-lived or are commonly embedded in other objects.
X AVOID defining a struct unless the type has all of the following characteristics:

• It logically represents a single value, similar to primitive types (int, double, etc.).
• It has an instance size under 16 bytes.
• It is immutable.
• It will not have to be boxed frequently.
  

Also:
I think I'll name my structs with lowercase letters.
Constant class... But things like "float", "unit" and other built-in  primitive value types
have lowercase letters. So I'll name my structs with lowercase letters.

How much is 16 byes?
1BYTE == 8BITS.
ARGB pixel = 32bits. Each channel is 8Bits. AKA: 32 bit color is 4Byte color.
How many pixels in 16 bytes?
Four. (4+4+4+4 == 16)
So, think of a struct as 4 pixels worth of data or less.

Invalid use of destructor foo as type

Bad Code:
~MyClass::MyClass(){

}

Good Code:
MyClass::~MyClass(){

}