[DUG] Is it a bug in latest version of Delphi?

[Edward Koryagin]

Versions of comctrl32.dll ??

Edward Koryagin


--- On Tue, 16/2/10, Kyley Harris <Kyley at harrissoftware.com> wrote:

> From: Kyley Harris <Kyley at harrissoftware.com>
> Subject: Re: [DUG] Is it a bug in latest version of Delphi?
> To: "NZ Borland Developers Group - Delphi List" <delphi at delphi.org.nz>
> Received: Tuesday, 16 February, 2010, 5:03 PM
> the fact that it behaves different under
> delphi 7 and Delphi 2007 on the same machine implies that
> there is some strange mystery at work in the compiled code
> that is not obvious. its not a direct problem of the
> underlying windows API.
> 
> As to using the GetLastError.. 
> There is issue I have with relying on that
> rather than the -1. The MSDN documentation states that not
> all routines need to or are required to call SetLastError(0)
> on success, and only set it on failure. the value -1 is what
> you are supposed to analyze to determine IF you should check
> GetLastError. GetLastError is not the first test. Clearly
> microsoft does not intend the storage to be used for
> negative values even if some appear to work.
> 
> if you rely on GetLastError rather than the -1.
> you may get a true value of "3" but getlasterror
> was not reset from some other call and you can get a false
> fail.
> 
> 
> 
> On Tue, Feb 16, 2010 at 4:55 PM,
> Karl Reynolds <kreynolds at chocfishsoft.co.nz>
> wrote:
> 
> On Tue, Feb 16, 2010 at 4:43 PM, Kyley
> Harris <Kyley at harrissoftware.com>
> wrote:
> 
> > I'll add my cents..
> 
> > under Delphi 7, getlasterror returns error 1413 as
> Karl said.. under Delphi
> 
> > 2007 no errors whatsoever. whats clear is that
> Getlasterror is unlreliable
> 
> > in this situation as Microsoft says, because microsoft
> online help says the
> 
> > getlasterror value cannot be controlled depending on
> OS and device and only
> 
> > the -1 is reliable as an answer.
> 
> 
> 
> Except that -1 isn't reliable because, as already
> discussed, it could
> 
> be a valid data value. I would in fact expect the code
> returned to
> 
> vary by OS and device (and that's what RaiseLastOSError
> is for) but I
> 
> really didn't expect there to be an OS or device on
> which an
> 
> LB_GETITEMDATA request out of the range of the listbox
> wasn't an
> 
> error! Evidently I'm too trusting or something.
> 
> 
> 
> Under the circumstances, checking the bounds first seems
> necessary.
> 
> 
> 
> Cheers,
> 
> Karl
> 
> _______________________________________________
> 
> NZ Borland Developers Group - Delphi mailing list
> 
> Post: delphi at delphi.org.nz
> 
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> 
> Unsubscribe: send an email to delphi-request at delphi.org.nz
> with Subject: unsubscribe
> 
> 
> 
> 
> -- 
> Kyley Harris
> Harris Software
> +64-21-671-821
> 
> 
> 
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> NZ Borland Developers Group - Delphi mailing list
> Post: delphi at delphi.org.nz
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to delphi-request at delphi.org.nz
> with Subject: unsubscribe