Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site psivax.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!psivax!friesen From: friesen@psivax.UUCP (Stanley Friesen) Newsgroups: net.lang.c Subject: Re: Function argument question Message-ID: <641@psivax.UUCP> Date: Mon, 12-Aug-85 16:36:52 EDT Article-I.D.: psivax.641 Posted: Mon Aug 12 16:36:52 1985 Date-Received: Sun, 18-Aug-85 03:47:01 EDT References: <555@brl-tgr.ARPA> Reply-To: friesen@psivax.UUCP (Stanley Friesen) Organization: Pacesetter Systems Inc., Sylmar, CA Lines: 17 Summary: In article <555@brl-tgr.ARPA> ART@acc.ARPA (Art Berggreen) writes: > > >One way to approach this is to pass a pointer to the char pointer in >the function call. You can then update the char pointer before the >function returns, and the return value of the function can be the >integer. > Another approach is to pass the function a second argument, a pointer to an int for the numeric result and actually *return* the new char pointer. This avoids using a pointer to a pointer. -- Sarima (Stanley Friesen) {trwrb|allegra|cbosgd|hplabs|ihnp4|aero!uscvax!akgua}!sdcrdcf!psivax!friesen or {ttdica|quad1|bellcore|scgvaxd}!psivax!friesen