🚀 go-pugleaf

)%
)%|  shimoda@rmi.de       `---'   The last remaining adventure      |
)%|  shimoda@gopnbg.UUCP  |O o|   since there are no more tigers:   |
)
)Please correct me if I am wrong, but doesn't this code fragment
)contain two Bad Things?  No Guru has yet responded, so I thought I
)would take a shot at sticking my foot in my mouth.
)
)It busy-waits.  There is no call to Wait(), or WaitPort() before the
)GetMsg().  Even  if you are busy-waiting only while looking for double
)clicks, you shouldn't.
)
)GetMsg() will return NULL if no message has yet arrived.  With the
)various 'if (imsg-> ... )' tests, you are then indirecting through
)address 0, which while not necessarily fatal, is sloppy and will quite
)likely break on any system with memory protection (unless it's a VAX :-).
)Even if you do call Wait(), you should not depend on GetMsg()
)returning something non-NULL.
)
)Andrew Heybey, atheybey@ptt.lcs.mit.edu     Room 509, 545 Technology Square
.-----------------------------------------------------------------.
Of course you are right both times. As I said, it was hacked down
online so forgive me if this caused any trouble. Next time I will
be more reliable.
I just left out anything except the DoubleClick-stuff.

Thank you anyway.

|  shimoda@rmi.de       `---'   The last remaining adventure      |
|  shimoda@gopnbg.UUCP  |O o|   since there are no more tigers:   |
|                       ==Y==   Doublebuffered async. I/O       _ |
|----------------------- `U' ------------------------------  _ // |
|  Good terminalpackages     begin with A: AmigaCall, A-Ta.. \//  |
`-----------------------------------------------------------------'