Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!etaylor
From: etaylor@wilkins.iaims.bcm.tmc.edu (Eric Taylor)
Newsgroups: comp.windows.x
Subject: Re: target type for int *
Message-ID: <3265@gazette.bcm.tmc.edu>
Date: 19 Dec 90 15:54:03 GMT
References: <9012190238.AA19006@andreas.wr.usgs.gov>
Sender: usenet@bcm.tmc.edu
Reply-To: etaylor@wilkins.iaims.bcm.tmc.edu (Eric Taylor)
Organization: Baylor College of Medicine, Houston, Tx
Lines: 20
Nntp-Posting-Host: wilkins.iaims.bcm.tmc.edu


In article <9012190238.AA19006@andreas.wr.usgs.gov>, gjw@ANDREAS.WR.USGS.GOV (Gregory J. Woodhouse) writes:
|> If I should want to pass an array of ints between applications via a selection
|> (instead of by using sockets as I have been doing), what should I use for a
|> target atom?  For arrays of chars there is XA_STRING, but it doesn't seem
|> right to use the same type for int arrays -- Indeed  I'm not so sure it 
|> wouldn't introduce portability problems.  Can anyone help me out?  Should I
|> just use XA_STRING?  Can/should I define a new target type?
|> 

What could you do with an int * anywhere but the program that
generated it?  Pointers are not portable bewtween programs.
An array of ints would be implemented as type
XA_INTEGER but with a length corresponding to the length of the
array.  (Shades of FORTRAN!)
--
					Eric Taylor
					Baylor College of Medicine
					etaylor@wilkins.bcm.tmc.edu
					(713) 798-3776