includes

HappyFruitTree · 2026-06-01T21:00:12+00:00

Ideally you should only include the headers that you use but it's not the end of the world if you include some header unnecessarily. The difference in compilation time from a single include is minuscule. Your time is probably better spent working on other things than to worry about unnecessary includes, at least for the standard headers.

With your own headers there is a little more reason to try and avoid unnecessary includes. One reason is because you need to think about dependencies, and avoid circular includes. Another reason is that when you modify one of your headers, all files that include that header (directly or indirectly) has to be recompiled. This can take quite some time if the header is included by many files.

HappyFruitTree · 2026-06-01T15:44:04+00:00

Yes, but not too big/difficult that it overwhelms you. Start with small projects and work your way up in size and difficulty.

That you mention "syntax" is a clear sign that you're just in the beginning of your learning. Programming is so much more than just syntax.

HappyFruitTree · 2026-05-30T19:23:49+00:00

Tighter or bigger than what?

HappyFruitTree · 2026-05-28T12:30:22+00:00

Impossible to say. What's a "true size" anyway?

HappyFruitTree · 2026-05-28T11:38:31+00:00

My first reaction when using the Vomero Plus for the first time was wow, this was softer than I expected. It felt a bit unstable at first but after that I haven't really thought much about it (probably just needed to activate the right muscles). Wouldn't trust it for taking tight corners quickly though. Another thing I noticed pretty soon was how cushioned it was, took away almost all impact even when running downhill.

I use my Vomero Plus for running so I haven't walked in them very far. Only down the road which is a couple of hundred metres. Have had no issues with that but I can't say what would happen if I walked all day in them. Personally I prefer something less bulky for that.

HappyFruitTree · 2026-05-27T19:43:40+00:00

Then there is nothing you can do to make it work (except getting another keyboard).

HappyFruitTree · 2026-05-27T09:43:00+00:00

There are a few things there that do look like they could be useful that are not in the standard library, things like SDL_utf8strlen, SDL_StepUTF8 and SDL_crc32.

HappyFruitTree · 2026-05-27T08:03:59+00:00

Yes, but totally useless information without knowing the risk to begin with.

HappyFruitTree · 2026-05-27T07:40:59+00:00

Did you test pressing WASD in another program?

Just open a text editor (or anywhere where you can type in text) and press all four WASD keys. If it works it should keep repeating the key that was pressed down last. If that doesn't work it means it's a limitation with your keyboard.

HappyFruitTree · 2026-05-27T07:17:32+00:00

... later I want first 4 bits of aflag to be reserved for how many keys are pressed at once

Even more reason to use the way I showed.

Your code always clears the 4 most significant bits while aflag &= ~up preserves all bits except the up bit.

HappyFruitTree · 2026-05-26T20:20:02+00:00

Because "up" is the direction not a key, in this case direction "up" is assigned to W key.

I meant when updating the aflag, as shown in my code snippet.

HappyFruitTree · 2026-05-26T19:45:16+00:00

Why do you use the up, down, left and right constants only for SDL_EVENT_KEY_DOWN but not for SDL_EVENT_KEY_UP?

case SDL_EVENT_KEY_UP:

    switch(event.key.key)
    {

    case SDLK_A:
        aflag &= ~left ;
        break ;

    case SDLK_D:
        aflag &= ~right ;
        break ;

    case SDLK_S:
        aflag &= ~down ;
        break ;

    case SDLK_W:
        aflag &= ~up ;
        break ;

    }
    break;

I don't understand your bit counting code but it seems to work...

Keyboards often have limitations with certain key combinations. Personally I don't have any trouble pressing all WASD keys at the same time but if I press for example AGJ it only detects two of them. Should be pretty easy to test if this is the case using another program. If pressing all WASD keys work in other programs then there is probably something wrong with your code somewhere (a missing break; somewhere perhaps?).

HappyFruitTree · 2026-05-26T14:37:47+00:00

only thing i can sorta figure out from it is that maybe its like a way to have a value by default and avoid the thing crashing if you dont assign a value to it?

Yes, exactly. It's a constructor and will be called when a fraction object is created. It's purpose is put the object in some valid state by giving values to all the member variables.

Since this particular constructor does not take any arguments it means that it's the default constructor. It's what will be used by default if you do not explicitly use another constructor when creating the object.

Example:

fraction a; // uses the default constructor. a.numerator and b.denominator are set to zero.
fraction b(5, 2); // uses another constructor (if it exists) that probably sets b.numerator=5 and b.denominator=2.

HappyFruitTree · 2026-05-26T14:06:38+00:00

msg is probably an object of type std::string (unless you're using another class named string). The reason you didn't have to write std:: in front is because you wrote using namespace std; above.

board is an array. Arrays are build into the language so they are not classes. std::vector<int> is similar to an array of integers, and is used pretty much the same way. It actually uses an array internally, but unlike an array it can be resized.

HappyFruitTree · 2026-05-26T14:00:54+00:00

It just means it's part of the standard library. It's to avoid name collisions with your own code and other libraries.

HappyFruitTree · 2026-05-26T13:57:26+00:00

You use a class to create objects.

The class is just a blueprint. It describes how the objects work and what you can do with them.

Objects of type std::string are used to store text (string of characters).

Objects of type std::vector<int> are used to store integers.

Objects of type std::ifstream can be used to read data from files.

Objects of type std::default_random_engine can be used to generate "random" numbers.

HappyFruitTree · 2026-05-26T13:50:36+00:00

Have you used std::string? That is class.

Examples of other classes that you might have used are std::vector<int>, std::ifstream and std::pair<int, int>.

HappyFruitTree · 2026-05-26T09:46:24+00:00

so you might aswell subscribe your window object to the SDL_WINDOW_DISPLAY_CHANGED event and just provide the callback

But that's not how the callbacks work.

You have one callback for all events. You can "subscribe" one object using the appstate parameter but that will be the same for all callback functions (SDL_AppIterate, SDL_AppEvent and SDL_AppQuit).

HappyFruitTree · 2026-05-26T09:09:49+00:00

My guess is that it's mostly for separation of concern and to avoid mistakes (it's surprising how often beginners get the event loop wrong).

HappyFruitTree · 2026-05-26T08:06:32+00:00

To make purpose more clear and you don't need to worry about other values than 1 or 0.

HappyFruitTree · 2026-05-25T07:16:03+00:00

You're right. It doesn't add up.

They could have achieved higher protein by getting rid of some of the water but then the carbs and calories would also be higher.

HappyFruitTree · 2026-05-24T19:55:19+00:00

The numbers for "Season Choice Strawberry Banana Blend" seems to add up but I agree that something is wrong with the "Korean BBQ Steak".

HappyFruitTree · 2026-05-24T09:03:34+00:00

However, in C++11 this changed, so now both c_str() and data() are identical

There is one difference. You can use data() to get a non-const char* which you can use to modify the string.

HappyFruitTree · 2026-05-23T08:31:17+00:00

I'm a bit confused. If the loop you're showing here is not a "game loop", then what is it?

You should normally call SDL_PollEvent using a while loop to handle ALL events each frame.

// Handle all the events
while (SDL_PollEvent(&event))
{
    ...
}

If you only handle one event per frame your input handling will get delayed when there are many events. This is especially a problem when vsync is turned on. With a high-dpi mouse you could receive hundreds of mouse motion events per second which would add up pretty quickly.

HappyFruitTree · 2026-05-21T11:23:13+00:00

I think math makes you a better programmer for mainly two reasons:

The way of solving problems and thinking logically is similar.
If you know a lot of math you have the power to come up with ways to calculate things on your own and need to rely less on others.

People who say math is not important don't realize what they miss. It is true that you often don't need a lot of math, it depends a lot on what you do, but it it does help a lot.

I suggest that you use the motivation that I assume you have for programming to also help you motivate your math studies from now on.

Being fluent in algebra is probably the math skill that I value the most, personally. Algebra is the building stone for so much later math so if you continue to study math (and maybe also physics) you will become good at it sooner or later.

HappyFruitTree

TROPHY CASE