It was just an example.

Yeah you could create pointers for doing nulls, but it would probubly make more sense to have some sort of default convention.

int MyInt = 0;
if(MyInt == 0)//equivalent to null

or if you need to use 0

int MyInt = -1;
if(MyInt == -1)//null

or if you need the entire integer

intMyInt = 0;
bool isIntNull = true;
//do work here
if(isIntNull)//int null, reguardless of the ints value

OR(it's pretty damn basic, and I just threw it together in notepad so it may not compile, but the idea would work)

template
class Nullable{
bool isNull;
theType Value;
public:
Nullable(){
isNull = true;
}
bool IsNull(){
return isNull;
}
theType GetValue(){
return Value;
}
void SetValue(theType val){
isNull = false;
Value = val;
}
};

Yeah, but a pointer isn't any specific type, it's a reference to a location in memory.

Ah ok. In natural C++ though, ints,bytes,chars,and bools aren't nullable as far as I've ever known.

If you're rewriting in c++ with the CLR you have Nullable types in which any object can be null(This is how most ORMs deal with ints and bools etc).

Well if you really have, you wouldn't be complaining about not knowing/understanding the terminology :p

This just shows that your problem isn't really with git, it's with you lack of knowledge of it. I'd imagine you're kind of a green horn to the technology, and you haven't quite figured out how all of these things actually benefit you, if you take a moment to learn them.