42
Comments
  • 7
    How hard can it be to place a breakpoint inside (or even just a log statement) and watch when it's hit?
  • 7
    @kamen are you trying to apply logic to a shitty meme?
  • 1
    @Kimmax If this is really taken from a piece of code, then it's not just a meme.
  • 4
    @kamen it's even easier doing a search for the function name. But can't expect those retarded meme shitters to think that far and besides their audience is as retarded as they are.
  • 2
    @molaram Now imagine that there is something like JavaScript's eval() that can call functions dynamically (so that you wouldn't be able to find it).
  • 3
    @kamen whoever use eval have much bigger problems i'd say
  • 1
    @molaram I'm not saying it's good practice, I'm saying it's possible.
  • 3
    @molaram No, there are a lot of frameworks that do all sorts of "magic", where something abstracted 3 or 4 levels deep will call a method based on the name of something else based on something dynamically set, or the existence of a file, or an environment variable. *cough cough rails devs*

    Doing a full grep for the function name, its permutations, etc is not going to turn up anything.
  • 1
    @madumlao +1 I remember that calling a function with a callback function which itself took either 3 or 4 arguments yielded different results.
    Wrapper((a, b) => a+b) and
    Wrapper((a, b, _unused) => a+b)
    Will make a difference...

    My linter warned me about ‘_unused’ being unused and I removed it. Then program crashed.

    My comment was:
    “Do not fucking remove that unused parameter. It will make the program crash!”

    You guys, guess the language (and the library making use of that phenomena)!
  • 5
    A fragile equilibrium of bugs and memory leaks somehow canceling each other out keeps this masterpiece alive
  • 1
    @uyouthe @uyouthe Isn’t that the essence of a program?
Add Comment