🚀 go-pugleaf

In article <1992Oct24.142015.21925@splunge.uucp> royce@splunge.uucp (Royce Howland) writes:
>dave@prim (Dave Griffiths) writes:
>
>It's certainly possible that NeXT didn't document things clearly enough,
>but in the case of the keyboard scan-codes example, one doesn't need to
>be a rocket surgeon to realize that there are probably other, more secure
>ways for an app to get keyboard input than reading the raw scan codes,
>whether one suspected ADB was coming or not.  Going to the hardware on
>any machine of this level of complexity is always a risk.

All fine and dandy, but I still don't know what the "blessed: way
of doing it is, and any mention of it in the docs is non-existent.

Furthermore, I have example code from NeXT that does it the 
non-OOPC (Object Oriented Politically Correct :-) way.
\

Someone please BROADCAST the OOPC way of doing it please, so we can
end this discussion!

- db

>-- 
>Royce Howland, DKW Systems Corp.   |  "And since OS/2 2.0 is a 32-bit
>       Everything is IMHO          |   operating system, programs are easier
>royce@splunge.uucp  (NeXTMail OK)  |   to write and run faster, too."
>or kakwa!atlantis!splunge!royce    |  ad for OS/2 2.0