Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!tut.cis.ohio-state.edu!magnus.ircc.ohio-state.edu!csn!ub!dsinc!netnews.upenn.edu!eniac.seas.upenn.edu!alex
From: alex@eniac.seas.upenn.edu (Edmund Davis)
Newsgroups: comp.sys.mac.apps
Subject: Re: Relational files in 4D
Message-ID: <37746@netnews.upenn.edu>
Date: 17 Feb 91 19:39:44 GMT
References: <9102141103.aa17479@PARIS.ICS.UCI.EDU> <37592@netnews.upenn.edu> <FRANCIS.91Feb15113318@wolfman.cis.ohio-state.edu>
Sender: news@netnews.upenn.edu
Reply-To: alex@eniac.seas.upenn.edu (Edmund Davis)
Organization: University of Pennsylvania
Lines: 25

In article <FRANCIS.91Feb15113318@wolfman.cis.ohio-state.edu> francis@wolfman.cis.ohio-state.edu (RD Francis) writes:

>
>Along the more or less lines, it's important to note that (unless it's
>one of the things that got changed with version 2.0) local variables
>($<varname>) don't carry their definitions into APPLY TO SELECTION
>commands; try replacing $new above w/ NewCoName or something like
>that, to get better results.
>--
>R David Francis   francis@cis.ohio-state.edu

Yes, in ver. 2.1.1, $var (local variables) do retain their values throughout
an APPLY TO SELECTION command.  I am not sure when exactly this was implemented
but I just tested it and it works fine.  (Although, I have had some
inexplicable difficulties with pointers and indirection along these lines...)

In the given example, you _probably_ could have simply specified the field
name itself, but I haven't checked this out.

alex
----
Edmund A. Davis			      Internet:	alex@eniac.seas.upenn.edu
ACIUS Registered Developer             US Mail:	233-F So. Melville St.
						Philadelphia, PA 19139
					  	(215) 386-3305