• (disco) in reply to Arantor
    Arantor:
    Don't forget [func_get_args()](http://php.net/manual/en/function.func-get-args.php) is a thing for really shitty overloading.
    \*runs screaming in terror*

    Give me good old-fashioned params (C#) any day.

  • (disco) in reply to Arantor
    Arantor:
    Don't forget func_get_args() is a thing for really shitty overloading.

    Ugh. At least you can set default values and avoid this shit. Unless you really want a function that can accept more parameters than initially planned without rewriting the function prototype. And who would ever want to use that kind of mindfuckery?

    No, don't answer.

  • (disco) in reply to Onyx
    Onyx:
    Ugh. At least you can set default values and avoid this shit. Unless you *really* want a function that can accept more parameters than initially planned without rewriting the function prototype. And who would *ever* want to use that kind of mindfuckery?

    No, don't answer.

    PHP developers before PHP 5 OOP was a thing? :laughing:

    This is the fucking legacy we have to put up with.

  • (disco) in reply to Arantor
    Arantor:
    This is the fucking legacy we have to put up with.

    "Let's create a new language, called PHP2, that fixes all the fuckuppery but is otherwise just like PHP. Oh, we'll probably have a problem until libraries get ported, so let's add a new function we can call that will allow PHP libraries to work in PHP2, even if they partake in the madness that was removed from PHP2."

  • (disco) in reply to FrostCat

    They are threatening to skip PHP 6 and go straight to PHP 7 only indulge in utterly retarded backwards compatibility breaking code for no reason other than because they can.

    For example, a private method would be defined as private function _myMethod(args)... and now they have proposed removing the word 'function' from that.

    Because it saves them typing. Not for any other reason - straight up BC break for laziness reasons only.

  • (disco) in reply to Arantor
    Arantor:
    They are threatening to skip PHP 6

    My soi-disant PHP2 was not to be construed as "PHP version 6", except for humor value by adding a compatibility mode.

  • (disco) in reply to Arantor
    Arantor:
    Because it saves them typing.

    I don't have a problem with that change, I don't think, as long as the parser can handle it. It's not as if C/C++/C# can't get by without that keyword.

    I have to admit I'm torn about the reason, because I don't see value in verbosity for its own sake. I get your complaint, though.

  • (disco) in reply to FrostCat
    FrostCat:
    My soi-disant PHP2 was _not_ to be construed as "PHP version 6", except for humor value by adding a compatibility mode.

    Except the sad truth is... that's kind of what PHP 6 was originally supposed to be when it was first pitched about 5 years ago.

    The whole point was to break out of this incremental bullshit and drop in things like proper sane Unicode support as a fucking core feature rather than this fucked up situation where you can do full Unicode provided you basically do it by hand or hope the relevant libraries are available.

    But then they decided to drop that because it was too big a task and they gradually whittled down the scope until it became what is ultimately PHP 5.3 with the revamp of the OOP stuff to include namespaces.

    As for dropping the word function, if there were a legitimate reason beyond 'it saves us typing the word', I'd be more supportive. Decrufting is good, after all.

  • (disco) in reply to Arantor
    Arantor:
    But then they decided to drop that because it was too big a task

    To be fair, it is a big task (assuming you want to get some reasonable amount of speed as well). It doesn't get smaller by letting it fester though.

  • (disco)

    I think this remains my favorite DailyWTF:

    public boolean checkFalse(Boolean bool)
{
  if (bool.booleanValue() == Boolean.FALSE.booleanValue())
  {
    return Boolean.FALSE.booleanValue();
  }
  else
  {
    return Boolean.TRUE.booleanValue();
  }
}

    It's the WTF that just keeps on giving1; you peel back one layer of WTF and there's another one underneath.

    It's not quite casting, but it feels in the same general vein to me as this submission.

    1 Like Discourse, which doesn't let me put that into a [quote] block.

  • (disco)

    Has anyone mentioned string.ToString() yet?

  • (disco) in reply to FrostCat
    FrostCat:
    Let's create a new language, called PHP2, that fixes all the fuckuppery but is otherwise just like PHP.

    Maybe they could ask the guys working on Perl 6 and Python 3* for some advice...

    * Ok, ok, to be fair Python 3 is probably ok. And released.

  • (disco) in reply to Onyx
    Onyx:
    Maybe they could ask the guys working on Perl 6 and Python 3* for some advice...

    Computer languages are proving to be just like human languages; getting anything changed, no matter how stupid, is an almost impossible undertaking. We refer to computing as though it was a subject with dramatic rates of change, but actually most people working in the field are deeply conservative. And the reasons are time, and money.

  • (disco) in reply to dkf

    Oh, no disagreement - but we're now 5 years down the road and the problem continues to be just as problematic as it was before at least from a core-dev perspective. Fortunately most of the good PHP devs already understand the limitations of dealing with WTF-8 in PHP by now and have libraries on hand that will do the job.

  • (disco) in reply to chubertdev
    chubertdev:
    Has anyone mentioned `string.ToString()` yet?
    Ehr, the FA?
    Finally, because ToString() is such a poorly-documented and poorly-understood call and you never know what type it'll give you, he casts its result to a string.
  • (disco) in reply to Onyx
    Onyx:
    Maybe they could ask the guys working on Perl 6 and Python 3* for some advice...

    <small>* Ok, ok, to be fair Python 3 is probably ok. And released.</small>

    Funny, I had the exact same thought. Python 3 dragged people in kicking and screaming, by dint of not abandoning the effort despite the first two iterations sucking ass. Now it's a hell of a lot better than 2.6 or 2.7 ever were, I give major props to Guido for sticking to his guns on that one and delivering, and only the most hidebound seem determined to stick to the deprecated version.

    Perl 6 and PHP 6 must be playing cards up in the sky with Winamp 6.

  • (disco) in reply to foxyshadis
    foxyshadis:
    I give major props to Guido for sticking to his guns on that one and delivering, and only the most hidebound seem determined to stick to the deprecated version.

    Exactly what I'd like to see PHP doing, so yeah, even though I made that joke you gotta respect Python devs for that.

    foxyshadis:
    Perl 6 and PHP 6 must be playing cards up in the sky with Winamp 6.

    Come now, Winamp is officially over. Perl 6, and likely PHP 6, will be in public beta any decade now...

  • (disco) in reply to Onyx
    Onyx:
    Come now, Winamp is officially over.
    If so, no-one's told Winamp themselves; they still think they'll release something this year…
  • (disco) in reply to RaceProUK
    RaceProUK:
    If so, no-one's told Winamp themselves; they still think they'll release something this year…

    Huh, I might have wrong info then. That happens when I go on hear-say I guess...

  • (disco)

    I like that word, "deathly". I'll put it on a sign: "Warning, deathly current!" and see what Google Translate makes of it.

  • (disco) in reply to Severity_One

    Let's see.

    @translator Warning, deathly current.

  • (disco) in reply to Arantor
  • (disco) in reply to VinDuv

    That thread is dead, I guess the deathly current killed it.

  • (disco) in reply to Arantor

    http://what.thedailywtf.com/t/deathly-current/7606/31?u=aliceif

  • (disco) in reply to foxyshadis
    foxyshadis:
    Perl 6 and PHP 6 must be playing cards up in the sky with Winamp 6.

    It's a pity we can no longer say "...and Duke Nukem Forever".

  • (disco) in reply to FrostCat
    FrostCat:
    It's a pity we can no longer say "...and Duke Nukem Forever".
    But we can still say *Half-Life 3*
  • (disco) in reply to RaceProUK
    RaceProUK:
    But we can still say Half-Life 3

    Yeah, rub it in, you bastard.

  • (disco) in reply to Arantor
    Arantor:
    @translator Warning, deathly current.

    won't work here BTW. for "reasons" threads started by blakeyrat or paulabean are ignored by my bots.

  • (disco) in reply to accalia

    PaulaBean, because of the links to articles, and Blakey, because Blakey :smile:

Leave a comment on “When You Really Want to be Sure it's an INT”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article