I have often used

if 1 = 2.

If I don’t want the code to be used, but want it to be available as active code. The only real reason I would want that is for a message to be found when using a where used if it is called dynamically.

Can’t think why you might use the reverse though.

Let’s break down the statement:
if cl_crm_ic_services=>greglemondmemorial = space.

This is an ‘if’ statement meaning we are going to make a decision here. They often look like this:
if
do something.
else.
do anthother thing.
endif.

The example above is just the if line where the condition is:
cl_crm_ic_services=>greglemondmemorial = space.
We are asking if something is equal to space.
‘Space’ in SAP speak is a reserved word meaning a blank variable.
So we are going to do something if some variable is blank. That variable is cl_crm_ic_services=>greglemondmemorial. This is a class or object (cl_crm_ic_services ) and a property or attribute ( greglemondmemorial ) of the class. The funny => means that it is a static attribute. Static means that you don’t have to create an object to get at the property – it is always available.
So this means we are asking if a variable that hasn’t been changed is still blank (its initial condition).

Did this help?
My question is: Why? and why choose the name greglemondmemorial? It is not really following any meaningful variable naming conventions.