Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!snorkelwacker.mit.edu!ai-lab!rice-chex!bson
From: bson@rice-chex.ai.mit.edu (Jan Brittenson)
Newsgroups: comp.sys.handhelds
Subject: Re: M/L Interrupts/Concurrent Routines
Keywords: ml, interrupts, concurrent routines
Message-ID: <15233@life.ai.mit.edu>
Date: 24 Apr 91 07:39:27 GMT
Article-I.D.: life.15233
References: <28106e62: 2851comp.sys.handhelds@hpcvbbs.UUCP> <1991Apr23.115645.9250@corpane.uucp> <72610@eerie.acsu.Buffalo.EDU>
Sender: news@ai.mit.edu
Organization: nil
Lines: 19

In a posting of [23 Apr 91 20:03:15 GMT]
   cloos@acsu.buffalo.edu (James H. Cloos) writes:

 > There must be a ML-level routine that can be used to call an xlib

Calling an XLIB is actually quite simple:

	move	pc, a
	add.a	xlib_ref-., a
	jump	@a
xlib_ref:
	data.a	#2e92
	data.3	700, 1


Will transfer control to XLIB 700 1.

						-- Jan Brittenson
						   bson@ai.mit.edu