How to write false $_REQUEST, please help

This is if statement $_REQUEST if the language translated

if ($_REQUEST[‘language’]) {
}

i need to set the opposite, if the language not translated, what its looks like, please help

which one is correct? or no one of them

if (!$_REQUEST[‘language’]) {
}

if ($_REQUEST![‘language’]) {
}

if !($_REQUEST[‘language’]) {
}

if (!$_REQUEST['language']) {
}

it can be set and still be empty?

isset() is slower than filter_has_var().

filter_has_var() also utilizes the user input rather than superglobals (PHP’s SAPI stores the input). The use of superglobals is not best practice. If I’m building something from scratch, I destroy the superglobals outright. That way if another developer comes along, they’re forced to access the input properly.

best practice? maybe for you. using isset is perfectly fine.

you’re this guy.

you saw someone doing it your way, and now tout it as the greatest thing ever… till you find yet another more convoluted way to do something simple.

You’re right. I’m the only person involved in web development that insists that accessing raw input data is a bad idea. I’m also the only person that prefers to use faster methods for accomplishing tasks. I’m just convoluted that way.

because filtering and then accessing has NEVER been done before.

This is if statement $_REQUEST if the language translated

if ($_REQUEST[‘language’]) {
}

i need to set the opposite, if the language not translated, what its looks like, please help

which one is correct? or no one of them

if (!$_REQUEST[‘language’]) {
}

if ($_REQUEST![‘language’]) {
}

if !($_REQUEST[‘language’]) {
}

if (!$_REQUEST['language']) {
}

it can be set and still be empty?

isset() is slower than filter_has_var().

filter_has_var() also utilizes the user input rather than superglobals (PHP’s SAPI stores the input). The use of superglobals is not best practice. If I’m building something from scratch, I destroy the superglobals outright. That way if another developer comes along, they’re forced to access the input properly.

best practice? maybe for you. using isset is perfectly fine.

you’re this guy.

you saw someone doing it your way, and now tout it as the greatest thing ever… till you find yet another more convoluted way to do something simple.

You’re right. I’m the only person involved in web development that insists that accessing raw input data is a bad idea. I’m also the only person that prefers to use faster methods for accomplishing tasks. I’m just convoluted that way.

because filtering and then accessing has NEVER been done before.