It's also worth pointing out they are not mutually exclusive. Your getEmplData() method can just call the "atomic" methods to build its struct.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Sean A Corfield > Sent: Monday, August 04, 2003 9:32 AM > To: [EMAIL PROTECTED] > Subject: Re: [CFCDev] Correct technique for a method call > > > On Monday, Aug 4, 2003, at 06:43 US/Pacific, Sparrow-Hood, Walter wrote: > > 1) A single method that returns all the data in a structured variable, > > as in: > > 2) Have multiple methods, one for each item of data (there could be up > > to a dozen items), and use: > > 3) Or a variation on #1, where I pass in the requested variable, as in; > > Is one approach 'better' or more correct from as deign perspective or > > does > > it just depend on one's preferences and particulars of the application? > > It depends. I would probably go with #2 unless I typically needed all > the employee data in a single struct in the client code to manipulate > it. > > Sean A Corfield -- http://www.corfield.org/blog/ > > "If you're not annoying somebody, you're not really alive." > -- Margaret Atwood > ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
