C++ Index

Delphi Index



Understanding C++ Operators

Translating C++ Code into Delphi Pascal


C++ has five binary arithmetic operators, which take two operands and two unary arithmetic operators, which can take one operand.  Five assignment operators can be created by combining these arithmetic operators with the equals sign to create 'assignment operators'.

The arithmetic operators are +, -, *, /, %, with the operators + and - having unary versions which require only one operand.  the assignment operators are +=, -+, *=, /+, and %=.

In Delphi the assignment operator is ' := ' while in C++ the assigment operator is simply ' = '.  This would be the equivalency operator in Delphi, while in C++ the equivalency operator is ' == '.  So in Delphi we would write ' if x = 16 then ' and in C++ this would be written as ' if (x==16) '.  In Delphi we would write ' x := y ' which sets x equal to y, and in C++ we drop the colon the perform the same operation ... ' x = y'.

The other relational operators are similar in both languages.  They are <, >, <=, >=, == and then in Delphi where we write  ' <> ' (not equal) in C++ this becomes ' != '.

The logical operators in C++ representing a logical AND, OR, and NOT as applied to boolean operands are ' && ', ' || ', and ' ! '.    There are also two logical assigment operators, ' &= ' and ' |= ' which perform and assign the results of a logical AND and a logical OR operation respectively.  For example,

x &= 2;

This would be similar to writing  ' x := x AND 2; '

One of the differences in a C++ logical test is that if the first test fails the second test may not be evaluated.  To accomplish the same thing in Delphi requires nested if - then statements (there is also a compiler option to turn off 'full boolean evaluation').

For example the following statement would generate an error in Delphi in the second part of the statement if Delphi is doing full boolean evaluation and x is equal to zero, due to an attempted division by zero...

if (x = 0) or (100 div x < 10) then

In C++ this statement would not generate an error, since, if x was equal to zero the test would be considered a success and the other conditional statements need not be considered...

if (x==0 || 100 / x < 10)

Similarly in the above example a test to ensure that x is not zero would not cause a crash if the or  relational operator was replaced by an 'and' relational operator.

In C++ you might see operators and operands combined in the following ways...

++x;

This is similar to writing inc(x) in Delphi, which means x := x + 1 (the difference being that the former generates more optimized code.

The increment operator can appear before or after the operand...

y = ++x;

y = x++;

In the first cause (pre-increment) x is incremented by one, and the result is then assigned to y.  IN the second case, x is assigned to y and then x is incremented by one.  

In Delphi we could write...

y := x; inc(x);

And in C++ this becomes...

y = x++;

An example of using an assignment operator in C++ ...

x /= z;

In this case two operands (x and z) are combined using an assignment operator.  This statement could also be written as ' x = x / z; '

Assignment operators can also be evaluated from right to left in a statement resulting in strange looking calculations like the following.  

x = y *= 10;

This is equivalent to following code...

y = y * 10; x = y;

When arithemetic operators are included multiple times in a single line the operators are evaluated from left to right if they have the same precedence, otherwise the operator with the highest precedence is evaluated first.  One way to get around memorizing the precedence of operators is to enforce precedence using brackets, in which case the rule is that the inner most bracket is evaluated first, then so on until the outer most bracket is evaluated.  For example, consider the following line of code without brackets.

x = y + z - q * 6 / t;

Both mulitiplication and division have a greater precedence than adding or substracting, and multiplication '  * ' and division ' / ' both have equal precedence so evaluating from left to right we get first q * 6 and then the result is divided by t.  Then once again working from the left we get y + z evaluated and then the previous results of the multiplication and division are subtracted from this result and the solution is then assigned to the variable x.  A change in precedence causes a change in results.  One way to ensure that the results are what you want is to use brackets.  

Let us suppose that first q should be subtracted from z and 6 should be divided by t and then these two results should multiplied together and then added to y.  To override precedence and get the results we wanted we would need to use brackets...

x = y + ((z - q) * (6 / t));

The two inner brackets are evaluated first, then the multiplication in the outer bracket is evaluated, the result of these operations are then added to y and assigned to the variable x.  This is considerably different than what would result if the rules of precedence were applied (indeed such a calculation would just about impossible to achieve without the brackets.

C++, like Delphi uses the ' dot operator ' to access fields of a record (on the stack) and a pointer operators to access variables on the heap.

In Delphi, assuming we have a record 'info' with a field 'age' we could access this using the dot operator if this was a static instance of the record (which would thus be on the stack, and not require a pointer).

x := info.age;

If info was dynamically created using a pointer we could access the fields using a pointer operator...

x := info^.age;

C++ also uses the dot operator for static records...

x = info.age;

To access a record on the heap (created with a pointer) the indirection operator in C++ looks like the following...

x = info->age;

Let us suppose that we have a pointer to an integer and wish to assign the value of the integer to a variable.  In Delphi the indirection operator would appear as follows...

x := intptr^;

In this case ' intptr ' is a pointer to an integer delcared as follows...

var intptr : ^integer;

In C++ the variable is declared as follows...

int* intptr;

And then the indirection operation looks like the following...

x = *intptr;

This is pretty much the same as in Delphi.

A short code segment illustrating how this works in Delphi...

procedure TForm1.Button1Click(Sender: TObject);
var px : ^integer;
x : integer;
begin

new(px);
px^ := 12;
x := px^;
showmessage(IntToStr(x));
end;


For a C++ example of the same sort of thing follow the link to the C++ section at the bottom of the page and consult the section on C++ pointers...

C++ also has a bitwise not operator  (the tilde ' ~ ')

x |= ~0x02;

What is meant is that this number will be combined with the variable x using a bitwise NOT operation (each bit subjected to a NOT operation, in otherwords reversed from 0 to 1 or from 1 to 0 before the OR operation is applied) and the result then assigned back to x.   This bitwise NOT operand is different than the logical NOT operand represented by the ' ! ' symbol, used in boolean expressions...

if (!something)

The scope resolution operator ( ' :: ') is discussed in the section on C++ Classes, and is the operand with the highest precedence.  

The table below illustrates operator precendence in C++ ... As you can see along with the field operators (used in structures) brackets then have the next highest precedence, for the reasons explained above...All operators in each group have equal precedence with assignment operators of equal precedence being evaluated right to left and other operators left to right as described above...(Therefore a bracket to the left of dot operator would have precedence, which makes sense...)

:: scope resolution operator

. (the dot operator), -> (pointer), [ ] (square brackets), ( ) (round brackets),  ++ and -- (post increment/decrement), and the various types cast operands

~ (tilde - bitwise not), ! (logical not), + and - (unary), ++ and -- (pre increment/decrement),  , & (the address of operator), * (dereference a pointer), the new, the delete, and the size of  functions

.* (the dot operator and the dereference operator), ->. (pointer operator and the dot operator)

* (as multiply), / , %

+, -

<< , >> (the assign out to and assign into operators, typically used in printing or file I/O)

<, >, <=, >= (the relational comparison operators)

==, != (equivalence test operators)

& (bitwise and)

^ (bitwise xor)

| (bitwise or)

&& (logical and)

|| (logical or)

=, +=, -+, *=, /+, %=, <<=, >>=, &=, |=, ^= (assignment operators)

? : (? is equivalent to 'then' and colon is equivalent to 'else' operator, with the lowest precedence so that everything is evaluated in the test statement  before either the 'then' or 'else' code is executed, which also makes sense)


Next Page - Scope of variables

C++ to Delphi Index      Delphi Index



A Unified Field Theory

failed_gravity_theory.gif - 10361 Bytes



The Unified Field Theory
is also available as a zip file ->
unified.zip

Introduction :The Pioneer Effect and the New Physics. A brief description of the new physics required to explain the 'Pioneer Effect', which is the constant deceleration of space craft as they fly through space.






Principles of Evolution: A Study in the Evolution of Bedbugs



A couple of years ago my bedroom was invaded by bedbugs. There were two variant genetic lines. One type of bedbug was an enlongated, thin, tubular insect, and the second genetic line was a flat, perfectly circular insect. The result of the cross breeding of these two genetically distinct variants was the production of a bedbug with charcteristics of both, an enlongated, flat bedbug with a central bulge (such that the shape of the bedbug was somewhere between 'long' and 'circular'). The long skinny bedbugs were such strange and unfamiliar looking insects that at first I did not recognize them as being bedbugs, and considered them to be a seperate species of insect. However, as the photographs of bedbugs above indicate, enlongated and skinny bedbugs are not uncommon, and the photographs also show the variants that are produced by genetic combinations that result in an insect somewhere in between 'circular' and 'enlongated'.

Therefore it is my hypothesis that evolution occurs by means of the transfer of dominate genes, with the production of such dominant genes being the product of 'biological algorithms', a genetic software program that brings physical characteristics into harmony with behavior, such that when behavior changes, and a conflict then exists, this acts as a trigger and causes the release of dominant genes. The result is rapid evolution of species. The bedbug is a relatively new insect, not the product of millions of years of evolution but rather an insect that is evolving in real time. The newly emerging dominant form of the insect is the flat, round ciruclar insect, well adapted to living in human bedrooms (it is flat, rather than tubular, thus allowing it to hide in the smallest cracks, living a stealthy lifestyle, and it is round, which gives the insect a maximum storage capacity such that it must endanger itself only a few times a month by emerging to feed.

Other examples of rapid evolution include the development of long legs in an invasive species of toad in Australia. As the toads move into the mountainous regions of Australia, and their behvaior changes, making them 'climbing toads', over the course of just a couple of decades the toads in the highlands have grown long legs specially adapted to climbing. It is worth noting here that the toads are poisonous, and are a successful invasive species because they have no natural predators in Australia, and so it would not be the case that the toads with long legs were 'the fittest survivors', because all the toads are survivors, and therefore predation does not explain the rapid emergence and spread of such well adapted, long legged toads. Once again we see evidence for the existence of biological algorithms and the rapid spread of dominant genes through a population, which once introduced proceed to overwhelm the older genes which are being replaced (making toad long legged and a bed bug round and flat).


A Theological Experiment

My interest in pursuing the Unified Field Theory is spurred on by my need to discover the theoretical explanation of a new form of propulsion (as explained on this page: Why the Unified Field Theory?). The experiment involving the bedbugs came out of nowhere.

I also believe that it is possible to justify theological propositions using experimental methods. If a thing is an objective truth then it can be verified and proven true by means of experimentation. Such a theological proposition is of more value than a ‘divine revelation’, since such revelations depend upon nothing more than establishing authority figures which requires the creation of artificial hierarchies, for the only reason why I might be encouraged to believe an authority figure who orders me to believe unsubstantiated opinions is if I could somehow be convinced that this authority possessed a mind that was somehow superior to mine, and thus was fit to express opinions as though opinions were unquestionable facts and thus worthy of being elevated to the status of absolute dogma.

There is a self evident human inequality which is visibly apparent. Some people are ‘beautiful’ and thus are the true elite on this planet, and some people are not. It is this sexual inequality and the degeneration that follows upon beauty that is the true driving force behind all the evil that happens on earth. The need for ruthless oppression and the pursuit of wealth and the consequent creation of suffering and poverty which must follow upon this practice is for the purpose of creating an artificial alpha elite.

The true elites are the young and the beautiful. The artificial elite are the rich and the wealthy. The elite aging rich artificial alpha male has no good looks, for he is physically degenerate, but he will be found escorting beauty because he has a beautiful wallet. If he loses his wallet he will be found at home with all the other unattractive aged beta males sitting in a rocking chair watching reruns of Bonanza. No money, no sex. It is for this reason that the alpha males are found to be so ruthless and so violent in pursuit of their goal. The alpha male has fallen. The beta male has arisen and now the whole planet is full of ruinous destruction for it.

We see in religion a confused and contradictory reaction to this reality. On the one hand religion preaches a sexless heaven where castration and the clitorectomy create ‘pure spirits’. Muslims throw women under sacks. On the other hand religion supports hierarchy and is the prop of the elite alpha male. It is for this reason that religion is incoherent when it comes to speaking about sex.

Now we see this same principle at work in all of nature. Guppies dance and show off their colorful tails and the guppy who dances with the most colorful tail is the sexually successful guppy. Therefore it is the doctrine of the ruthless oppressor which teaches that the solution to human sexual violence is to be found in castration and the creation of pure ghosts. This would be equivalent to damning an aardvark for having the ‘sinful aardvark nature’ or prosecuting an anteater for the high crime of ‘ant genocide’.

Therefore it was my theological hypothesis that the correct solution to this problem is to give every guppy a beautiful colorful tail. I compare this solution to the classic religious solution which is to cut off every tail since having a tail is ‘sinful’. If having a tail is sinful then God must be sinful for no human being has any choice in deciding whether or not they would be born with a colorful tail, or whether they would not.

When I was young I was a beautiful guppy with a lovely tail. So everyone seemed to think. I am older now. My nose became very badly sunburned and destroyed. It seemed good to me to test my hypothesis by using these ‘biological algorithms’ to correct this problem. I healed half my nose as you can see by the line separating the still very dark patch on the side in the photograph below.





I documented my experiment on these pages. one two t hree four fi ve six


I have confirmed to my own satisfaction that my theological proposition is correct and that religious dogma is erroneous, being based as it was upon nothing more than ‘divine revelation’ which is just a form of opinionated speculation. For the time being I am not continuing this experiment, for I must wait until the weather on this planet improves, and the dark clouds of ruthless oppression break letting a little sun shine come through so that I can show the world the truth about God, by showing people how God goes about giving an old guppy back his beautiful colorful tail.


Until then I will have to sit on the sidelines, while all my scientific breakthroughs are deliberately ignored, while I wonder to myself what ever in the world could be wrong with the human race, because what this all will prove at the end of it all is that there definitely was something wrong with the people on this planet.