• javasux@lemmy.worldEnglish
    53·
    2 months ago

    bruh why is unsucked a global variable

    also that function shouldn’t be named Check if it does things other than checking (e.g. sucking)

    • Programmer Belch@lemmy.dbzer0.comEnglish
      20·
      2 months ago

      Could be inside a class for something to be sucked, making unsucked a variable for the class. CheckAndSuck would be a better name for the function. I don’t think the meme needed a code audit but here I am.

      • davidagain@lemmy.world
        6·
        2 months ago

        Your naming advice is universally good.

        However, if this was a functional programming language, there wouldn’t be any mutable global variables to be unaware were being examined, nor could Suck do any sucking unless it were passed the thing to suck and returned the sucked thing.

        In this way the subtle class of bugs that you both are warning against would be impossible to introduce.

        Depending on the kind of sucking that Suck does, however, you may perceive the global invisibility and availability of the sucking as an advantage in this case. But possibly not if the code is your girlfriend/boyfriend.

        • Programmer Belch@lemmy.dbzer0.comEnglish
          8·
          2 months ago

          I didn’t need to do this but I did and now I want it in my comment history:

          class Suckable {
    bool unsucked;

public:
    Suckable () {
        unsucked = true;
    }

    void Suck() {
        unsucked = false;
    }

    void CheckAndSuck() {
        if (unsucked) {
            Suck();
        }
    }
};

          Sorry for making you see c++, it’s the language I’m currently using. This program compiles on my machine and doesn’t use global variables.

          • davidagain@lemmy.world
            41·
            2 months ago

            Indeed, indeed.

            No need to apologise for posting c++ in the channel. The programming world owes a lot to Prof. Stroustrup. I enjoyed your reply a great deal.

            You have two choices: firstly, a regular regular attribute, where you can Suckable myThing; and myThing.CheckAndSuck; etc to your heart’s content, and indeed no global variables are being sucked.

            But you can also declare static bool unsucked; and what is a class variable if not a global variable by another name?

            In fact, what is to stop your innocent-sounding accessor method from nuking the filesystem or calling memLeak.recurse();?

            I’m not sure that these things keep you up at night, but you have my sympathy if they do.

            If there was anything I could do to help you relax after a stressful day of multiple inheritance and manual memory management, I would.

            Well, except that of course. I mean, we all draw the line somewhere.

            Unless we’ve had too much to drink or smoked too much weed, in which case boundaries seem less important at the time.

            One time in college, my friend…

            but no, that’s another story for another thread.

  • Cralder@lemmy.worldEnglish
    53·
    2 months ago

    Bad naming practice. CheckSuck implies it only checks and returns the result. Everything the function does should be included in the name to avoid confusion. Call it SuckIfUnsucked or something

    • needanke
      8·
      2 months ago

      That was my first reaction as well. Even if you say you can see that it doesn’t return a bool it’s still ambiguus as to what (if anything) happens when the state is sucked/unsucked. I would also prefer a name like GuranteeSucked or EnsureIsSucked.

  • bi_tux@lemmy.world
    14·
    2 months ago

    RWIIR!!!

    edit: here, I did it for you:

    use std::*;

static mut sucked: bool = false;

fn main() {
        unsafe {
                check_sucked();
        }
        println!("Kris has been sucked is {}", sucked)
}

unsafe fn check_sucked() {
        if !sucked {
                suck();
        }
}

fn suck() {
        sucked = true;
}

    edit 2: fixed it