Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!haven!purdue!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!unido!rmi!infoac!infohh!shimoda From: shimoda@infohh.rmi.de (Markus Schmidt) Newsgroups: comp.sys.amiga.tech Subject: Ultimate Wait-GetMsg strategy (?) Message-ID: <494@infohh.rmi.de> Date: 7 Feb 89 18:57:39 GMT References: <890204105857.21000bb9@elcc.epfl.ch> Reply-To: shimoda@infohh.rmi.de (Markus Schmidt) Organization: RMI Net * Aachen/Hamburg/Flensburg * W.Germany Lines: 18 Hi! Every time using a Wait-GetMsg-pair I thought how to do it best way. Now I think I got it: while (1) { while (!(imsg= GetMsg(win->UserPort))) Wait (1<UserPort->mp_SigBit); ... select imsg->Class and break when ended ... } I think that should ship around all "oddities" like multiple Messages arriving or NULL-msges arriving?! Any comments? Markus