compiler behavior and help text inconsistent
Posted: Fri Jul 15, 2022 3:17 pm
I'm surely thinking too much but i'm always defensive when programming. I.e. if a procedure has a return value, then I also observe it accordingly.
This brings me to the Topic: Dealing with return values when compiler and help are different, or better they are not really different, but only differently accurate.
How to deal reasonably with properties that work "better" than described in the help.
Do we have to assume that this property will disappear without notice?
-- Probably yes.
So what are the alternatives?
Two topics that keep catching my eye:
This brings me to the Topic: Dealing with return values when compiler and help are different, or better they are not really different, but only differently accurate.
How to deal reasonably with properties that work "better" than described in the help.
Do we have to assume that this property will disappear without notice?
-- Probably yes.
So what are the alternatives?
Two topics that keep catching my eye:
Code: Select all
hwnd = OpenWindow(#Window_0, <all other parameter>)
; compiler -> correct window handle
; Help -> nonzero ... can sometime just be #True
; use instead
if OpenWindow(#Window_0, <all other parameter>)
hwnd = WindowID(#Window_0)
iDC = StartDrawing(<Something>)
; compiler -> correct device context
; Help -> nonzero ... can sometime just be #True
; use instead
; my educated guess
dc = CreateDC_("DISPLAY", 0, 0, 0)
hdc = CreateCompatibleDC_(dc)
SelectObject_(hdc, <hImage>)
