[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linrad] Re: Memory leakage.



Hi Richard,

> One of the principal ideas in C++ is to encapsulate the object and 
> present a consistent interface
> 
> If XCreateFontCursor is a class (it may not be)
> the class code will be often in a header file say "xCreateFontCursor.h" 
> and a code file say "xCreateFontCursor.cpp" (However they might be 
> buried in another file somewhere)
> 
> The header will declare the various parts of the object (attributes) 
> which may consist of functions and data objects such as variables. Some 
> of the attributes may be other objects
> It will assign "access rights" eg public, private to the various attributes.
> The code for each function will be in the .cpp file
> At least One function will be a constructor named
> 
> XCreateFontCursor ::XCreateFontCursor ()
> 
.
.
.
> There is (usually) a destructor
> 
> XCreateFontCursor ::~XCreateFontCursor ()  // (note the ~)
OK. There is not - not according to the C++ naming convention
anyway. There is not even a single occurance of :: in any of
the X header files.

> The destructor code should make sure the object is properly destroyed 
> when no longer required.
> It looks as though different functions are called here to create and 
> destroy the object so it is probably not in C++!
> As another poster says, it is probably not a mission critical issue at 
> this point if the leak is small
OK. I will let that be the final on this thread. The Linrad leaks are 
small and associated with X11 system calls. I will just forget them:-)

73

Leif / SM5BSZ

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <linrad@xxxxxxxxxxxxxxxxxxxxx>.
To unsubscribe, E-mail to: <linrad-off@xxxxxxxxxxxxxxxxxxxxx>
To switch to the DIGEST mode, E-mail to <linrad-digest@xxxxxxxxxxxxxxxxxxxxx>
To switch to the INDEX mode, E-mail to <linrad-index@xxxxxxxxxxxxxxxxxxxxx>
Send administrative queries to  <linrad-request@xxxxxxxxxxxxxxxxxxxxx>

LINRADDARNIL