Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!amdahl!meccts!viper!john
From: john@viper.UUCP
Newsgroups: comp.sys.atari.st
Subject: Re: help! vro_cpyfm, vrt_cpyfm
Message-ID: <709@viper.UUCP>
Date: Sat, 21-Mar-87 09:44:22 EST
Article-I.D.: viper.709
Posted: Sat Mar 21 09:44:22 1987
Date-Received: Sun, 22-Mar-87 21:40:53 EST
References: <8703171353.AA13091@ucbvax.Berkeley.EDU> <1987Mar18.014408.23167@gpu.utcs.toronto.edu>
Reply-To: john@viper.UUCP (John Stanley)
Organization: DynaSoft Systems
Lines: 23
Keywords: vro_cpyform

In article <1987Mar18.014408.23167@gpu.utcs.toronto.edu> 
pete@gpu.utcs.UUCP (Peter Santangeli) writes:
 >
 >[well written description of vro_cpyform...]
 >

 >...(vro_cpyfm is similar, so I will stick with vro_cpyform)....

Mind telling us what the differences are (if any)?

 >	"pxyarray" is a standard GEM input array which describes the 
 >offsets and sizes of the rectangles within each memory area described by
 >the MFDB's that will be transfered.

You give enough details for all the -other- parameters that someone could
use the function without needing further documention.  How about describing
pxyarray so other people will know enough to use it??
(Why tell people just enough to -almost- be able to use it?)

--- 
John Stanley (john@viper.UUCP)
Software Consultant - DynaSoft Systems
UUCP: ...{amdahl,ihnp4,rutgers}!{meccts,dayton}!viper!john