1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Suggestion More clear PMMP Branches?

Discussion in 'Suggestions' started by XdmingXD, Jun 3, 2017.

  1. XdmingXD

    XdmingXD Baby Zombie

    Messages:
    151
    GitHub:
    xdmingxd
    I (or many other members) always get confused to those branches
    for example,master(202) , spammy-backtrace , api3/blocks etc.
    What are those branches , what is that mean?
    I don't really get it because it can only tell us that it is passed and Dev #??? o_O
    So, maybe it can add more informations like version tag (V1.0.9) or any other things?
    Thx :D
     
  2. jasonwynn10

    jasonwynn10 Wither Skeleton Verified

    Messages:
    1,194
    GitHub:
    jasonwynn10
    The master branch is the only branch that non-developers need to worry about. All the api3 branches contain rewritten bits of the software for better performance or easier feature additions. event-call-shorthand is for developers to call events easier. spammy-backtrace is for debugging NBT and Encapsulated Packet errors which would normally go unnoticed. skip-ticks is to allow for better performance on slower machines by skipping ticks if they take longer than 50ms.
     
  3. SOFe

    SOFe A-Team Staff Member PMMP Team Poggit Admin

    Messages:
    1,248
    GitHub:
    sof3
    Branches != Tags
    Tags = releases
    Branches = it is in development and should be merged into master eventually.
     
  4. TheDiamondYT

    TheDiamondYT Zombie Verified

    Messages:
    262
    GitHub:
    TheDiamondYT1
    != !== !==

    (!= doesnt equal !==)
     
  5. SOFe

    SOFe A-Team Staff Member PMMP Team Poggit Admin

    Messages:
    1,248
    GitHub:
    sof3
  6. TheDiamondYT

    TheDiamondYT Zombie Verified

    Messages:
    262
    GitHub:
    TheDiamondYT1
  7. SOFe

    SOFe A-Team Staff Member PMMP Team Poggit Admin

    Messages:
    1,248
    GitHub:
    sof3
    And I thought I was the author and I had the right to decide the set of operators I use :D
    Moreover, there is no absolute preference between === and ==. As long as you know what you're doing, the safest one is the preferred one.
    In addition, I was using = not ==, which isn't something you can compare with!= in PHP anyway ;)
     
  8. Awzaw

    Awzaw Zombie Pigman Poggit Admin Verified

    Messages:
    579
    GitHub:
    awzaw
    I just assumed SOFe was keeping the language as BASIC as possible :D
     
    Last edited: Jun 19, 2017
  9. TheDiamondYT

    TheDiamondYT Zombie Verified

    Messages:
    262
    GitHub:
    TheDiamondYT1
    Very punny
     
  10. SuperMaXAleX

    SuperMaXAleX Baby Zombie

    Messages:
    108
    GitHub:
    SuperMaXAleX
    Never understand why === is encouraged than ==
     
  11. Sandertv

    Sandertv Zombie Pigman

    Messages:
    744
    GitHub:
    Sandertv
    Take str_pos as an example, it returns false if the string hasn't been found, or the location of it if it has been found. The location could be 0, if it's at the start of the string. Checking if the output == false would evaluate to true even if the string was found but on the first position, checking if the output === false would evaluate to the correct output.
     
  12. SOFe

    SOFe A-Team Staff Member PMMP Team Poggit Admin

    Messages:
    1,248
    GitHub:
    sof3
    It would have made more sense if identical operator was made == and the equal operator was made ~~ (something like ≈) since it just means "similar".
     

Share This Page