I'd love to know exactly what the problem was, so i could say, hey get
this ***.dll and fix their problems that way. The code that generally
gave the errors was when using DeviceCapabilities to find printer Info,
maybe it was just bad print drivers (this of course would not be
un-common)?
-----Original Message-----
From: Carl Reynolds [mailto:[EMAIL PROTECTED]]
Sent: Monday, 9 October 2000 4:47 p.m.
To: Multiple recipients of list delphi
Subject: RE: Re: RE: [DUG]: Creating PChars
Yes, well GetMem is a very fundamental procedure. I mean, the VCL is
full
of calls to GetMem - Delphi would really fall apart without it (no
dynamic
array usage would be safe, for example). Obviously you have to watch
your
step when using it, but if I'd had the number of problems that (I infer)
you've had with it, then I'd suspect that that there was a corrupt
version
of borlandmm.dll being propagated around. Might that be a possibility?
Cheers,
Carl
>From: Jason L. Coley [mailto:[EMAIL PROTECTED]]
>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?
------------------------------------------------------------------------
---
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"
