Well I guess you have me there, although i'd like to know exactly why a
procedure will die on one machine and not another, when both machines
supposedly have the same operating system fixes etc?
And the culprit is always the GetMem and FreeMem. What else are you
supposed to do other than simply not use the commands.
Why have an application generate errors using a supposedly straight
forward procedure like Getmem, if you can avoid it?
-----Original Message-----
From: Nello Sestini [mailto:[EMAIL PROTECTED]]
Sent: Monday, 9 October 2000 2:57 p.m.
To: Multiple recipients of list delphi
Subject: Re: RE: [DUG]: Creating PChars
"With great power comes great responsibility"
- Stan Lee
Apologies for not posting this to the web group <g>
ns
-----Original Message-----
From: Carl Reynolds <[EMAIL PROTECTED]>
To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
Date: Monday, October 09, 2000 08:46
Subject: RE: RE: [DUG]: Creating PChars
>Yes, using PChar, or any pointer type, is dangerous. Using classes is
also
>dangerous - classes are really just pointers, and can point to nothing,
you
>can free them twice, and generally cause all sorts of trouble for
yourself.
>
>To take your argument to its logical conclusion, would you advocate not
>using classes because records never show errors and "work, plain and
>simple"?
>
>Cheers,
>Carl
------------------------------------------------------------------------
---
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
