On Tue, 28 Jan 2003, 1LT John W. Holmes wrote:
> > > Basically, what I'd like is to be able to post a form element with
> > > id="myvariable.whatever" and access it on the next page with
> > > $_POST["myvariable.whatever"].
> >
> > // obviously this is some busted garbage
> > $name.Array["first"]="Chris";
> > $name.Array["last"]="Wesley";
> > $name=$name.Array["first"]." ".$name.Array["last"];
>
> That assumes register_globals is ON, though, which isn't recommended. If you
> read the questions, the poster talks about using the value such as
There aren't two different lexigraphical parsers if you turn
register_globals on or off. So, PHP either allows ALL variables to have a
"." in their name, or disallow it altogether. So, moving outside of the
narrow case of POST variable names is what I did *after thoroughly reading
and thinking about the question*. (Somebody missed the Lex & Yacc hint.)
> $_POST['name.Array'], which is valid. Since it's encouraged to have register
> globals OFF, I think they should do aways with this period to underscore
> thing, also. It will only jack up people's code that rely on
> register_globals and they should be changing it anyhow.
As long as it's possible to turn register_globals on, this will have to be
a problem. I'd vote for tearing this bandaid off, getting rid of
register_globals altogether, and undo all the idiosyncrasies it causes,
but that's just me (and others who think similarly).
~Chris
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
