Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!cbmvax!phillip
From: phillip@cbmvax.cbm.UUCP (Phillip Lindsay CATS)
Newsgroups: comp.sys.amiga
Subject: Re: Message ports in 68000
Message-ID: <1764@cbmvax.cbmvax.cbm.UUCP>
Date: Mon, 27-Apr-87 09:18:19 EDT
Article-I.D.: cbmvax.1764
Posted: Mon Apr 27 09:18:19 1987
Date-Received: Tue, 28-Apr-87 01:26:40 EDT
References: <8704260218.AA05317@cogsci.berkeley.edu>
Organization: Commodore Technology, West Chester, PA
Lines: 25

in article <8704260218.AA05317@cogsci.berkeley.edu>, bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt) says:
> 
> 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.

NO!!! 
	In almost every call you make to DOS *that* port is used.

BTW, What happens if a TASK wants to create a port with your exec_support code?
==============================================================================
Phillip (Flip) Lindsay - Commodore Business Machines - Amiga Technical Support
  UUCP: {ihnp4|seismo|caip}!cbmvax!phillip      - Phone: (215) 431-9180
  No warranty is implied or otherwise given in the form of suggestion or 
  example. Any opinions found here are of my making.