My Fucking Simple BIG TIC TAC TOE Game

['Bruno]

It's not necessary to use a class there. It's just that the code could be improved (a lot), but that comes with practice and time. Don't worry too much about it. You will eventually improve with time. : )

[VirtualSia]

Nice going. Again you edited my comment, I'm starting to think you have a sexual relationship to Virtual Void.

[Lyoto Machida]

It's not necessary to use a class there. It's just that the code could be improved (a lot), but that comes with practice and time. Don't worry too much about it. You will eventually improve with time. : )

Thanks for some good news XD

[VvITylerIvV]

Yes, no need for classes here.

But CLEARLY, this code could be minimized to probably 300-400 lines of code easily just using for loops.

But aside from that, good job.

[Lyoto Machida]

Yes, no need for classes here.

But CLEARLY, this code could be minimized to probably 300-400 lines of code easily just using for loops.

But aside from that, good job.

I know , but i dont like to use mutch loops, cause it lags..

[VvITylerIvV]

I know , but i dont like to use mutch loops, cause it lags..

Meh, it'd be a LOT neater.

But, if you really are so against using loops. I've found a few ways to remove many lines of code (at least 50-60) without loops.

But I'm at school and can't really do much right now. :P

EDIT:

Oh, and I also found a way to make the UI a bit more appealing, by adding a few more lines of code. But meh, it's a great program all in all.

And I just noticed, you use if (Player == 'x' || Player == 'X');

Why not use the toupper function?

Player = toupper(Player);

PLUS! It gave me a GENIUS idea to make an RPG on a console application.

[NoShame]

lol nice game but its so boring

[Lyoto Machida]

Meh, it'd be a LOT neater.

But, if you really are so against using loops. I've found a few ways to remove many lines of code (at least 50-60) without loops.

But I'm at school and can't really do much right now. :P

EDIT:

Oh, and I also found a way to make the UI a bit more appealing, by adding a few more lines of code. But meh, it's a great program all in all.

And I just noticed, you use if (Player == 'x' || Player == 'X');

Why not use the toupper function?

Player = toupper(Player);

PLUS! It gave me a GENIUS idea to make an RPG on a console application.

Well almost the same thing anyway :P
btw Thanks for the help

[VvITylerIvV]

Nah, thank you for showing me the getasynckeystate is usable in console applications. I never realized that...

[Fovea]

Loops aren't slow.

if (GetAsyncKeyState(VK_SOMETHING) & 0x800)

Thats the proper way to check for a key press.

[VvITylerIvV]

Loops aren't slow.

if (GetAsyncKeyState(VK_SOMETHING) & 0x800)

Thats the proper way to check for a key press.

for loops are somewhat slow... A LITTLE slower than placing the code there, but makes the code a lot more easy to manage and read.

(seeing as they have like 2 more checks every time they do the code, it slows it down unnoticeably unless you time them both for about 40 hours or so...)

[Fovea]

Any loop can and will be unrolled by the compiler if deemed necessary.

[Lyoto Machida]

Loops aren't slow.

if (GetAsyncKeyState(VK_SOMETHING) & 0x800)

Thats the proper way to check for a key press.

The other way works too, but why that & 0x800, and difference?

[Fovea]

Return Value

Type: SHORT

If the function succeeds, the return value specifies whether the key was pressed since the last call to GetAsyncKeyState, and whether the key is currently up or down. If the most significant bit is set, the key is down, and if the least significant bit is set, the key was pressed after the previous call to GetAsyncKeyState. However, you should not rely on this last behavior; for more information, see the Remarks.

Although the least significant bit of the return value indicates whether the key has been pressed since the last query, due to the pre-emptive multitasking nature of Windows, another application can call GetAsyncKeyState and receive the "recently pressed" bit instead of your application. The behavior of the least significant bit of the return value is retained strictly for compatibility with 16-bit Windows applications (which are non-preemptive) and should not be relied upon.

Woops, its 0x8000 not 0x800. 0x8000 is a bit mask checking if the highest bit in the return value, which is a short, is set.

[VvITylerIvV]

If your using getasynckeystate in more advanced ways, not including 0x8000 will screw up your program due to this new thing called multithreading which wasn't around when getasynckeystate was created.

So if it has a chance to screw up your program, you SHOULD have enough experience to know how to fix it. Logically.