Re: Delphi Dot Net, Better than Win32, or just Hype?


"Pete Goodwin" <bdn.REMOVE@xxxxxxxxxxxxxxxxxxx> wrote in message
news:43ccb8fa@xxxxxxxxxxxxxxxxxxxxxxxxx
> Steve Zimmelman wrote:
>
>> I'm curious about dot net opinions. I may be wrong, but it seems dot
>> net is more a political marketing tool than something really worth
>> going after.
>>
>>
>>
>> How is it really better than a Win32 app?
>>
>>
>>
>> -Steve-
>
> That's what I'm debating. After putting together a minimal C# app and
> watching it run in 20MBytes of memory, compared to a full blown Delphi
> WIN32 app running in 5MBytes, I couldn't help thinking "bloated"?

Are you sure?
I have made a .net 2.0 server app a couple of months ago (TCP server and
Database access) and with about 10 clients connected it used about 11 MBytes
of ram.
even after running for a couple of weeks it was still using that amount of
memory.
That is the nice thing about the GC.

I am doing some work now on a Win32 Delphi app now and I was wondering how
to solve this:

When using a factory class that gives objects that contain some data... when
you are done with that object... should you clean it up or is it the
responsibility of the factory class?
When using Dotnet the GC takes care of that...
Sometimes in Win32 it's a bit dodgy who is responible of cleaning up
Objects... the factory class or the user of the objects.
For example: I was using a XML class that returns Node objects.
Internally it parses a XML document to a tree of Nodeobjects, when you
request a node it returns a pointer to that node.
So at one point I cleaned up the node I received after using it, by doing
that I broke a branch in the XML tree.
In another case I use a ASTM LIS class that returns ASTM records as objects,
in this case I DO have to clean up the received objects or I get memory
leaks...

Is there a rule I can follow here?


Best Regards,

Jeroen Vandezande



.