[geos-devel] Re: geos-devel Digest, Vol 12, Issue 5

[Yury A. Bychkov]

I think we can safely ignore most of the _DEBUG and new #includes. They are most
likely added by C++.Net automatically and don't perform any functions that we
need.
As for the memory fixes, I'd like to take a look at them before we add them to
the CVS. Paul, can you forward me Xie's file?

Yury

----- Original Message ----- 
From: "Paul Ramsey" <pramsey at refractions.net>
To: "謝　京平" <jingping.xie at jicoux.com>
Cc: "GEOS List" <geos-devel at geos.refractions.net>
Sent: Monday, October 06, 2003 8:25 PM
Subject: [geos-devel] Re: geos-devel Digest, Vol 12, Issue 5


> I looked through the diff against my source tree here at home.  There
> are 44 xie entries, and a couple of unmarked places as well which look
> like memory fixes. (Someone smarter than me will need to verify them.)
> There is also a bunch of stuff like this:
>
> +
> +#ifdef _DEBUG
> +   #undef THIS_FILE
> +   static char THIS_FILE[]=__FILE__;
> +   #define new DEBUG_NEW
> +#endif
> +
> +#ifdef _DEBUG
> +#ifndef _INC_CRTDBG
> +#error Missing include "Supports debugging features of the C runtime
> library."
> +#endif
>
> And lots of new includes to this header:
>
> +#include "../headers/stdafx.h"
>
> Can I assume this is .Net stuff we can safely ignore?
>
> Paul
>
>
> On Monday, October 6, 2003, at 07:39 PM, 謝　京平 wrote:
> > I am Jingping Xie.
> >
> >  I change the source a little.
> >  1.change it to library.
> >  2.amend some memory leak.
> >  3.create test program by .NET 2003.
> >
> >  you can search by "xie" to find where I amend.
>
>
> _______________________________________________
> geos-devel mailing list
> geos-devel at geos.refractions.net
> http://geos.refractions.net/mailman/listinfo/geos-devel