C++ Index

Delphi Index



File I/O in C++

Translating C++ Code into Delphi Pascal


C++ handles basic file I/O using streaming classes, from which instances of a streaming variable are created.  There is a similar feature in Delphi - TFileStream.

For example we could declare a file streaming variable in Delphi as follows...

var
  FileStream : TFileStream;
begin
   FileStream.Create('c:\something.txt', fmOpenWrite or fmCreate);
   FileStream.write(buffer, count);
   FileStream.free;
end;

In C++ the same thing would be accomplished using the classes ofstream, ifstream, and fstream.

Ofstream handles output, ifstream handles input and fstream handles input and output.  FStream seems similar then to the file variable in Delphi.

var
 AFile : file;
 amt : integer;
begin
 Assignfile(AFile, 'c:\somefile.brg');
 Reset(Afile, 1);
 Blockwrite(Afile, buffer[1],  200, amt);
 ....
 Blockread(Afile, buffer[300], 12, amt);
 ....
end;

In the above example the untyped file 'AFile' is opened using 'Reset' and is set to one, which means that the 'record size' for writes is one byte.  The Blockwrite statement begins writing at 'Buffer[1]' , writes out 200 bytes, and then returns the number of bytes written in 'amt'.  Later, aftering 'seeking' a spot in the file more than likely, the same file variable is used to read into the buffer.  Reset allows both read and write, similar to the fstream variable in C++.  TFileStream also allows either read or write or 'fmOpenReadWrite' which also mimics fstream in C++.

The following is an example of using the ifstream variable in C++ to write out a file.

remember to include the line #include <fstream.h> at the head of the source file...

Let's assume that we have created a character buffer to store the input...

char buffer[1024];

We need to create an instance of the ifstream class...

ifstream AFile("c:\somefile.txt");

A line can be read in as follows ...

Afile.getline(buffer, sizeof(buffer));

The destructor for the class closes the file if it is still open or you can explicitly close the file yourself...

Afile.close();

The code above passes a PChar (pointer to a character array) to the constructor of the ifstream class.  It is also possible to use the following line to open a file...

ifstream.Afile;
AFile.open("c:\somefile.txt");

One thing to watch out for if you are a Delphi programmer is that C++ uses double quotes for literal strings while Delphi uses single quotes.

To write to a file you can create an instance of the ofstream class, and then use the ' << ' operator to send output to the file.

ofstream.Afile("c:\somefile.txt");
AFile << "Write out this line please" << endl;
AFile.close;

The 'endl' means write end of line, or a return carriage.

Like TfileStream the streaming classes in C++ have modes that can be used to describe how the file is to be manipulated.  These modes are members of the 'ios' class and are specified as in the following example...

ofstream.Afile("c:\somefile.txt", ios::binary);

The default mode (if none is specified) is textfile mode.  The other modes are :

ios::app   - append to end of file...

ios::ate   - seek end of file on opening...

ios::in     - open file for input, used with the fstream class...

ios::out   - open for output...

ios::trunc - erase and rewrite the file, which is the default...

If more than one of these is used they are seperated by the bar character (which means 'or'), as follows (note that with TFileStream in Delphi these are seperated by the keyword 'or')...

fstream.Afile("c:\somefile.txt", ios::app | ios::out | ios::binary);

An example of reading a file in and then writing it out using a string variable in C++...

#include <fstream>
int main()
 {
    ifstream readfile("c:\readfile.txt");
    ofstream writefile("c:\writefile.txt");
    string thetext;
    while (getline(readfile, thetext))
      {
          writefile << thetext << endl;
      }
    readfile.close();
    writefile close();
  }

This program does nothing but read the file in and write it out again, and if the file was to manipulated this would of course be included in the while loop code.  Note that when only one line is included in a while loop (if/then construct, for loop etc) the curly braces are not strictly required and the line could be written as...

    while (getline(readfile, thetext)) writefile << thetext << endl;

As well when the file stream variables go out of scope the file stream class automatically closes the file if it has not already been closed, so the two close statements might not be really required either, but I include them here because it seems like good form.

In Delphi records can be rewritten to disk using the Blockwrite function of an instance of an untyped file variable whose default record size has been set to the size of the record in question.  One of the tricky parts of writing out records is that internally everything is kept aligned along double word boundaries for the sake of modern CPUs (which run fastest when operating with 32 bits).  So a record with a byte, a byte, and an integer which have the one byte bytes aligned along a 4 byte (double word) boundary to increase CPU performance, which means that when you try to write out the record to disk you can wind up writing out crap (and wondering what went wrong) if you fail to keep this in mind.  For example we are assuming here that TheRecord exists and we want to write it to disk...

var afile : file;  amt : integer;
begin
  Assignfile(afile, 'C;\somefile.txt');
  Rewrite(afile, sizeof(TheRecord));
  Blockwrite(afile, TheRecord, sizeof(TheRecord), amt);

As I mentioned, 'sizeof(TheRecord)' might not turn out the way you would expect because of that business with the 4 byte boundaries in internal memory representation of the record.  As well, just a tip, when you write out a buffer always refer to 'buffer[0]' in the Blockwrite statement (assuming zero is the beginning of the buffer, since writing from 'buffer' will write out a bunch of crap starting from whatever the address of the buffer pointer is, rather than starting from the address contained in the buffer pointer, which is what you want...

var afile : file; amt : integer; buffer : array[0..79] of char;
begin
   Assignfile(afile, 'c:\something.txt');
   Rewrite(afile, 1); {set record size to one byte}
  Blockwrite(afile, buffer[0], 80, amt);

In this example the record size (in the rewrite procedure) was set to one byte.  If we set the record size to 80 then we could write Blockwrite(afile, buffer[0], 1, amt); and write out 80 bytes this way as well.  

Let's assume that a record (or structure in C++) exists which has a name field followed by two integers, and we will refer to it as theRecord.  The structure can be written to disk as follows...

ofstream afile("c:\somefile.txt", ios::binary);
afile.write((char*)&theRecord, sizeof(theRecord));

The code (char*) is neccesary to 'cast' the record to a PChar which is required by the fstream write function.  If you are familiar with using the Windows API in Delphi you know that Delphi strings must be cast to pointers to character arrays as well (Pchar(TheString) in Delphi code).

The code &theRecord extracts the address of the record and so the bytes in the record starting from this address are cast to a PChar and then this PChar is passed to the write routine and written out to afile.  This accomplishes basically the same thing as the Delphi code above and this could also be done using the TFileStream class in Delphi, passing the number of bytes in the record structure as the argument to the writebuffer method of the streaming class.  (For some reason I am not clear on, the writebuffer method works while the write method does not, but this could have something to do with the way the internal addresses are used in these two methods).  As well, note that if you are reading in a record from disk you must use the same code as above, casting the record structure to a PChar, since the read function of the ifstream class also requires a character pointer as its operand.

When a file is open for read or for read/write it is possible to do random access on the file using the seeking functions provided by both Delphi and C++.  (Note that in Delphi you cannot seek using a textfile but rather you must use a typed or, as in the examples above, an untyped file variable).  Assume that afile is an untyped file variable...

var afile : file;  fpos : longint;
begin
   Assignfile(afile, 'C:\something.txt');
   Reset(afile, 1);
   fpos := sizeof(theRecord) * 122;  
   Seek(afile, fpos);

The Tfilestream class also has a seek method...

var filestream : TFilestream; offset : longint; origin : word;
begin
    filestream := TFilestream.create('c:\something.txt', fmopenread);
   filestream.seek(offset, origin);

Typed and Untyped files can return their file postion using FilePos which returns a longint...

lx := FilePos(afile);

As does TfileStream...

lx := filestream.position;

In C++ the fstream class has a seek function and a file position function, for either the ifstream or the ofstream classes.  Seekg() and tellg() seek or return the position for ifstream variables while seekp() and tellp() do the same for ofstream classes.  The usage of the functions looks like the following...

ifstream afile("c:\something.txt", ios::binary);
int pos;
afile.seekg(0, pos)
pos = afile.tellg();

By opening a file in append mode tellg() would return the size of the file in bytes.  By opening an ofstream variable in read/write mode parts of a file could be accessed and changed randomly.


Previous page - Passing by reference or value     Next page - Header interface files

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.