Re: [DUG]: Component Creation 101

2000-11-29 Thread Kurt
Regarding 4 doesn't the application free _all_ its assigned memory when it is closed? Or would some component that was constructed with a nil owner keep using that memory until some other event - if so, when would that be - reboot/shutdown/next Delphi app started ? I'm aware this is not a nice

Re: [DUG]: Component Creation 101

2000-11-29 Thread Neven MacEwan
PROTECTED] To: Multiple recipients of list delphi [EMAIL PROTECTED] Sent: Thursday, 30 November 2000 09:30 Subject: Re: [DUG]: Component Creation 101 Regarding 4 doesn't the application free _all_ its assigned memory when it is closed? Or would some component that was constructed with a nil owner

Re: [DUG]: Component Creation 101

2000-11-29 Thread Kurt
Neven MacEwan wrote: Kurt I assume you are basing this on the fact that any app written for Win32 gets 'shut down' at least a few times a day? g Heh, bring on Kylix... Also dynamically created comps may (create/free) for the life of the app so you would be coding and memory 'leak'

[DUG]: Component Creation 101

2000-11-28 Thread Neven MacEwan
Chrissy Just a few basics 1/ In Delphi you almost never have to use pointers and new() is really for non-object use 2/ A TComponent derived class can own other TComponents (which may own other...) See TComponent.Components array TComponent.ComponentCount (simarly TWinControl implement