Curious PHP error



  • In my latest script PHP Interpreter told me, what's wrong with my script:

    Notice: Unknown: Skipping numeric key 0. in Unknown on line 0



    Notice: Unknown: Skipping numeric key 1. in Unknown on line 0



    Notice: Unknown: Skipping numeric key 2. in Unknown on line 0



    Notice: Unknown: Skipping numeric key 3. in Unknown on line 0



    Notice: Unknown: Skipping numeric key 4. in Unknown on line 0



    Notice: Unknown: Skipping numeric key 5. in Unknown on line 0



    Notice: Unknown: Skipping numeric key 6. in Unknown on line 0



    Notice: Unknown: Skipping numeric key 7. in Unknown on line 0



    Notice: Unknown: Skipping numeric key 8. in Unknown on line 0



    Notice: Unknown: Skipping numeric key 9. in Unknown on line 0



    Notice: Unknown: Skipping numeric key 10. in Unknown on line 0

     

    I can't say it was very helpfull ... 😉



  •  Post your script, I dare you 😉



  • Do I smell an eval?



  • @MrOli said:

     Post your script, I dare you 😉

     

    Well, I'd settle for just seeing line 0.

     



  • from a language that has an "unexpected T_PAAMAYIM_NEKUDOTAYIM" error, yours seems quite sane, even as unhelpful as it is.



  • @lanzz said:

    from a language that has an "unexpected T_PAAMAYIM_NEKUDOTAYIM" error, yours seems quite sane, even as unhelpful as it is.
     

    That error message stems from PHP's Israeli-led development. Pa'amayim Nekudotayim is the English transliteration of the Hebrew phrase for "double colon."  Why they didn't translate it is beyond me, but the error makes sense if you understand Hebrew...

     

    [edit] Wikipedia has something to say



  • You're probably using some kind of opcode cache.  In PHP "on line 0" means the error was thrown somewhere inside the PHP interpreter/VM itself instead of in normal, parsed code.

     

    Oh, and "thenewone" is a recursive acronym for "thenewone posts crappy threads". 



  • @asdfdsa said:

    @lanzz said:

    from a language that has an "unexpected T_PAAMAYIM_NEKUDOTAYIM" error, yours seems quite sane, even as unhelpful as it is.
     

    That error message stems from PHP's Israeli-led development. Pa'amayim Nekudotayim is the English transliteration of the Hebrew phrase for "double colon."  Why they didn't translate it is beyond me, but the error makes sense if you understand Hebrew...

     

    [edit] Wikipedia has something to say

    It also makes sense if you have access to the Internet and about 10 seconds to look it up.  It's hardly an obscure error.



  • @lanzz said:

    from a language that has an "unexpected T_PAAMAYIM_NEKUDOTAYIM" error, yours seems quite sane, even as unhelpful as it is.
     

     It's the most Googlable error ever. I always hate "error 100" error messages that mean Google will likely give you lots of unwanted results.



  • @asdfdsa said:

    @lanzz said:

    from a language that has an "unexpected T_PAAMAYIM_NEKUDOTAYIM" error, yours seems quite sane, even as unhelpful as it is.
     

    That error message stems from PHP's Israeli-led development. Pa'amayim Nekudotayim is the English transliteration of the Hebrew phrase for "double colon."  Why they didn't translate it is beyond me, but the error makes sense if you understand Hebrew...

     

    [edit] Wikipedia has something to say

    Thats great because in America everyone speaks Hebrew! I would think SOMEONE in the corporate world would have thought "Maybe its time to localize PHP into english... maybe..."... eh?


    Edit: I know nothing of PHP and am glad for it, therefore I ban all flames that come after this post... Discuss.



  • @astonerbum said:

    Edit: I know nothing of PHP and am glad for it, therefore I ban all flames that come after this post... Discuss.
    I know nothing of copyright law and am glad of it, so I ban the police from doing anything to me because I downloaded The Dark Knight the night before it came out.  I AM INVINCIBLE.

    Or maybe I've been reading the Spore thread too much.  You know, whatever



  • @astonerbum said:

    Thats great because in America everyone speaks Hebrew!
    Right. You should localize all of PHP to Spanish right now!



  •  @morbiuswilters said:

    Oh, and "thenewone" is a recursive acronym for "thenewone posts crappy threads". 

    No, that would be "thenewonepct".



  • @PSWorx said:

     @morbiuswilters said:

    Oh, and "thenewone" is a recursive acronym for "thenewone posts crappy threads". 

    No, that would be "thenewonepct".

    I was mocking the tag on the OP, since it isn't recursive anyway.  That tag was actually created by pstorer to be ironic and joking, but thenewone took it seriously, I guess. 



  • @morbiuswilters said:

    thenewone took it seriously, I guess. 
    Why guess the improbable?

    "Seriously" ? ...



  • @asdfdsa said:

    That error message stems from PHP's Israeli-led development. Pa'amayim Nekudotayim is the English transliteration of the Hebrew phrase for "double colon."  Why they didn't translate it is beyond me, but the error makes sense if you understand Hebrew...

    Ah, but we've known for long time that weird foreign-language error messages aren't always clear, especially in OSS libraries / interpreters / development packages that will inevitably be used internationally. This problem was discussed by the Linux user community back in 1996, when we didn't quite have the web stuff yet, but the kernel was the biggest focus of the development:

    > I want nice German error messages telling me that the root filesystem
    > crashed :-).

    "Wurzel-Ordner-System gekracht."

    Please don't.



  • @shakin said:

    @lanzz said:

    T_PAAMAYIM_NEKUDOTAYIM
     

     It's the most Googlable error ever.


    so the existence of google justifies using random languages for your error messages? let's just replace ALL errors and warnings with GUIDs and then just use google to find out what they mean, instead of, i don't know - provide useful and readable error messages directly?



  • @lanzz said:

    so the existence of google justifies using random languages for your error messages?
    I know, right?  Damn those Israelis and their random languages!



  • That's a bit of a stretch, comparing to the use of GUIDs. It's not like PHP doesn't output something like

    <font face="courier new,courier">syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM, expecting T_VARIABLE or '$' on line N</font> or something to that effect.

    Sure, the mention of T_PAAMAYIM_NEKUDOTAYM may make you scratch your head, but since it is clearly pointed out that it's a parse error what you're dealing with, it shouldn't be too difficult to find your problem on that line.

    I guess what I'm just trying to say is: it could be better, but it still isn't as bad as throwing numeric-only exceptions (see also: Microsoft).



  • @bstorer said:

    @lanzz said:

    so the existence of google justifies using random languages for your error messages?
    I know, right?  Damn those Israelis and their random languages!


    your comment could have been relevant if php allowed localizing its error messages in different languages, hebrew being one of them. throwing in small chunks of unidentified (to the general public) language into an otherwise entirely english-language system is not justifiable by anti-antisemitism.



  • @lanzz said:

    throwing in small chunks of unidentified (to the general public) language into an otherwise entirely english-language system is not justifiable by anti-antisemitism.
    Who said anything about anti-antisemitism?  They guys who wrote the Zend engine were Israeli, and they used a Hebrew term for it.  Maybe it's confusing to you, but it's not a big deal.  It's clearly defined in both the list of parse tokens, and in the manual, and, let's be honest, hardly that much less clear than other error messages in PHP and every other programming language on the planet.



  • @lanzz said:

    your comment could have been relevant if php allowed localizing its error messages in different languages, hebrew being one of them. throwing in small chunks of unidentified (to the general public) language into an otherwise entirely english-language system is not justifiable by anti-antisemitism.

    Anti-anti-semitism?  WTF? 



  • @morbiuswilters said:

    Anti-anti-semitism?  WTF?
    Isn't that the same as zionism?


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.