Topic: Fuck you PHP!

[micah]

curious, what would you expect the outcome to be, casting a string as an integer?

[Mike]

Doing something similar in Python throws an exception.  That is what I would expect.  Or return null as that would signify that the operation failed.

[micah]

ah, i see what you mean. Yeah, PHP can be pretty lenient with things that you'd think shouldn't work.  Learning typescript now and I'm seeing how strict other languages can really be.  It's a bit eye-opening.

[Mike]

Fuck you PHP!


php > echo "ajdfkladfklajfk"['success'] == true;


Results:

Code: [Select]

Warning: Illegal string offset 'success' in php shell code on line 1
1

Seriously?  Fuck you!

It is because the ['success'] in the above case returns `a`.

Does turn out that `=== true` does return false.

[micah]

what are you even trying to do with that shit-code? Some context might help understand why this seems like a misguided error

[Mike]

Well, obviously that is not the actual code

This was part of the following:

    $options = [
        'http' => [
            'header'  => "Content-type: application/x-www-form-urlencoded\r\n",
            'method'  => 'POST',
            'content' => http_build_query($data),
        ],
    ];
    $context  = stream_context_create($options);
    $result = file_get_contents($url, false, $context);


The URL being called should have returned a JSON response which includes a `success` key that is a boolean.  However, due to the recent cutover the URL now returned a HTML string and the code continued on as normal like nothing was wrong.

Unfortunately, this is embedded in Wirepress code so I'm stuck with PHP for awhile

And now I've got to go and see if it ever worked and the best way to fix it.  /sigh