🚀 go-pugleaf

Hmmm, I've got a rather bizzare problem which I can't seem to figure 
out.  I'm writing a MDI program with OWL which holds an image in
the MDI children.  Each child window is derived from TWindow.

Now before I create the child window, I run a parsing function to
extract information for the image file header.  I need buffers to
manipulate the header, so I did the following:

	char* buffer = new char[80];
	...code for parsing...
	delete [] buffer;

When I use this code, I get a GPF in kernel.exe at the end of the child
window constructor.  Remember, the parsing code is executed before the
child is created and is even in a different module.  Also, this
error does not occur every time.  Sometimes, Windows will lock instead
of giving a GPF, but this is rare.

The problem disappears completely when I declare:

	char	buffer[80];

instead at the top of the parsing function.  

I'd rather allocate the buffers dynamically, but I can't figure
out why this fails.  I'm new to C++ so maybe there's something I'm
missing.

Sigh, any ideas or helpful hints are appreciated.

 

--
Ed McCreary                                               ,__o
mccreary@sword.eng.hou.compaq.com                       _-\_<,
"If it were not for laughter, there would be no Tao."  (*)/'(*)