Mailing List Archive


Back to the month index Back to the list index
Corey Sanders (csanders@entropy.muc.muohio.edu)
Tue, 6 Apr 1999 23:30:55 -0400 (EDT) 

Date: Tue, 6 Apr 1999 23:30:55 -0400 (EDT)
From: Corey Sanders <csanders@entropy.muc.muohio.edu>
Subject: Re: Lite / Form Question
Message-ID: <Pine.LNX.4.04.9904062113260.8134-100000@entropy.muc.muohio.edu>

Well,

What you've presented here is wonderful. Let me be the first to give it
full support. I hadn't considered adding the derefernce aspect. It is a
nice way of handling the possible memory issue I brought up.

While your adding things, is there any possibility of adding a defined
operator/function? It doesn't seem like it would be that difficult to add
a routine that checks to see if a variable exists in the symbol table. I
can usually take care of the defined functionality with the comparison
$var == "", but an actual defined operator would be cleaner to read and
would work for cases where the $var in question exists and is equal to "".

Keep up the good work,
-- Corey

On Tue, 6 Apr 1999, David J. Hughes wrote:

>
>
> On Wed, 31 Mar 1999, Corey Sanders wrote:
>
> > More realistically, from looking at the code, would be to have an array
> > that contains all the form data. That, coupled with the existing system,
> > could create a large memory footprint, but the ability to access form data
> > as a set of information would be valuable.
>
> One thing we've been playing with in the research code is dereferenced
> variables. So you can do something like
>
> $varName = "$foo";
> $varValue = $$varName;
>
> Also, we've looked at providing an array of all the form data variable
> names being passed into a script. That way you could do something like
>
> $loop = 0;
> while ($loop < # $W3MSQL_DATA)
> {
> $val = $$W3MSQL_DATA[$loop];
> $loop++;
> }
>
> If this sort of thing is important to the userbase then it'll make it into
> the 2.1 code.
>
>
> Bambi
> ..
>