🚀 go-pugleaf

Hello!
I had an Problem using the gcc for C++ some days ago.
It seems to be a Bug, and I can descripe it exactly now.

I used a class s_list containing memory structures and functions 
returning s_list. 
For example:


s_list operator =(s_list);

No Problem to compile this, but at runtime there are is a Problem.

s_list t,f;
Program calls t=f;

and gets stackmemory for arguments, returnaddress, and result.
The funktion calculates the result, an objekt of the class s_list. 
This result lives in the stackmemory.
When the funktion = is ready, the result form stack is copyed from stack
to datamemory of t using memcpy. The destructor for res is called, 
(this is the Bug) and the memory controled by res is lost.

Solution: 
   
s_list  &operator =(s_list);
        ^
        Thisway, no desructor is called.

Bye
  Harald.


--
Harald Leszke,Goerzalle 131/305,D-1000 Berlin 45, Tel: +49 (0)30 8178570

Wer mit 18 noch kein Kommunist ist, hat kein Herz!
	Und wer mit 28 noch Kommunist ist, hat keinen Verstand.