Deprecated means that it has fallen out of favor, and is
_in_the_process_of_being_phased_out_ You should not rely on this code in
new applications. Go look it up in a dictionary.
If you have to be backward compatible with < 4.1.0 (which was released
on 10-Dec-2001!) I suggest something like this:
<?
function get($v) {
$_GLOBALS[$v] = (version_compare(phpversion(), '4.1.0', '>=')) ?
$_GET[$v] : $HTTP_GET_VARS[$v];
}
get('desired_var');
echo $desired_var;
?>
However, I don't think it's at all unreasonable to request that they use
a version of PHP less than 2 years old (i think 4.0.6, the last version
before 4.1.0, was released 27-Jun-2001). At that point, I would be more
concerned with compatibility with _future_ releases than 'absolute
compatibility' with past releases.
On Wed, 2003-05-28 at 04:46, Jay Blanchard wrote:
> [snip]
> To maintain absolute compatibility, just use $HTTP_GET_VARS. It's
> availalable in all PHP versions, just deprectaed in versions here $_GET
> is available.
> [/snip]
>
> Just to be perfectly clear on this. Let's say that I am writing an
> application that I am going to release to the public (for free of
> course!). In order that the application be as compatible with the many
> installed versions of PHP as possible I should always use $HTTP_GET_VARS
> or $HTTP_POST_VARS ? Or is there a point at which the formation of the
> variable call changes (like the $_GET and $_POST in the latest
> versions)? If there is a point at which it changes how can I account for
> that in code, other than telling the potential use that "you must be
> running PHP 4.x.x"?
>
> Thanks!
>
> Jay
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
