Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!mit-eddie!genrad!decvax!ucbvax!COGSCI.BERKELEY.EDU!bryce
From: bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Message ports in 68000
Message-ID: <8704260218.AA05317@cogsci.berkeley.edu>
Date: Sat, 25-Apr-87 21:18:56 EDT
Article-I.D.: cogsci.8704260218.AA05317
Posted: Sat Apr 25 21:18:56 1987
Date-Received: Sun, 26-Apr-87 22:44:00 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18

Some time after writting a complete hyper-tiny replacment for the
exec_support library in	68000 I	realized that my purpose of opening a
message	port could be served far easier; each process has an associated
pre-allocated message port that	can be had quite simply:
-
-	move.l	 4,a6
-	suba.l	 a1,a1
-	jsr	 _LVOFindTask(a6)
-	add.l	 #pr_MsgPort,d0
-
Now is this being clever, or will problems crop	up later?  Every bit
of sample code that needs a port for Packets or	other uses creates
a custom one.
 
PS. Two requests by mail gets exec_support in 68000 posted to comp.sources

   //
\\// Save the sanity of millions, ban the BPTR!!