Monday morning code...

Pass pointers by value for the win......?

Monday mornings should be referred to as the "Hours of the n00bpocalypse"

it's saturday morning, this code doesn't cause a crash, but is just an stupid oversight i caught myself doing:

Tile *World::GetTile(unsigned int x, unsigned int y){ //Same as above, but we can specify x/y coordinates instead of index positions.
    if(x<0 || x>=m_Width ) return nullptr;  //We check that the x-axis is inside the world.
    if(x<0 || y>=m_Height) return nullptr; //We check that the y-axis is inside the world.
    return m_Tiles+(x+y*m_Width);
}

completly idiotic on my part, unsigned numbers are never less than zero;-)

One can never be sure enough! :P

Also check if nullptr is actually null.

Might want to fix the second x < 0 to y < 0 too. I mean, it doesn't change anything, but at least it looks right

If this was C++ there would be some chance of success due to operator overload, but...

I usually avoid writing any code monday morning, think about stuff, do some testing, identify issues and think of solutions... only start coding after lunch

I once made this "beauty" at work...

// Write
bool result = insert(results, data);

if ( m_CurrentSet )
{
       result = result || insert(*m_CurrentSet, data);
}
 

The idea was to store the latest of anything that has been written to file in memory, to make sure the latest set of data was in memory. However, this being a real time application, which in theory should run forever (and generates data for a multi-million dollar service), the results were pretty poor.

No harm done, since this was in a test and not production.

I ALWAYS end up making two comparisons on X or using X value for both X and Y on something, hahahaha, eventually have some reeeeallly weird behavior and track it to that, lmao

One can never be sure enough!

Also check if nullptr is actually null.

nullptr is a C++11 keyword that is guaranteed to be null.

Here's some recent Monday-morning like code

if (ddl.SelectedValue == "Ticket")
   LoadPassengerList(currentTrainNumber.Text);
   PassengerPanel.Visible = false;
 

See what I did there......?

See what I did there......?

Judging from your formatting, I'd say you forgot to put parenthesis after the if, so that the third line was executed regardless of the selected value? If so, it would be interesting what the results of this was

Just a wild guess, I'd say the PassengerPanel became invisible regardless of whether the selected value was "Ticket" ;)

One can never be sure enough!

Also check if nullptr is actually null.

nullptr is a C++11 keyword that is guaranteed to be null.

That was the point of my comment Comparing if unsigned values are negative... checking if nullptr is null... rings a bell?

Here's some recent Monday-morning like code

if (ddl.SelectedValue == "Ticket")
   LoadPassengerList(currentTrainNumber.Text);
   PassengerPanel.Visible = false;
 

See what I did there......?

Classic. "Hey, I just need to add one more thing in this if case... *copy, paste, compile*, no error, I'm such a good programmer! *moves on*"

2 weeks later, someone else: "Why is this stupid thing vanishing all the time? "