gjw@ANDREAS.WR.USGS.GOV (Gregory J. Woodhouse) (12/19/90)
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? ----------------------------------------------------------------------------- Gregory Woodhouse |We know that the center of the earth gjw@andreas.wr.usgs.gov |is a fiery molten mass...but it's not (415) 329-4694 (office) |good to dwell on it. (415) 325-7802 (home) | U.S. Geological Survey / 345 Middlefield Rd. MS 977 / Menlo Park, CA 94025 -----------------------------------------------------------------------------
etaylor@wilkins.iaims.bcm.tmc.edu (Eric Taylor) (12/19/90)
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