Using the win32-console the not-so-usual way

[foxman]

Hey,

I'm sharing a little application I have worked on these last days. Nothing exceptional, especially for the ones who aren't new to programming. But it might be interesting for the newer ones. Especially for those who tought you couldn't do anything "interesting" with the "console". Or those who have never used system specific functions.

Here's the link to the web page
win32console-labyrinth

I had the idea while browsing MSDN. I though about "hey, I don't know if it would work" and decided to write a little program (only as a proof of concept).

[By the way, don't look too much at the code, especially the design, it's bad from start to finish. I'm quite new to C++ (but not C).].

[MacGyver]

LOL.... Wow, that looks..... just from the screenshot.... like it would be messy code....

Looks like you had fun writing it, though.

[foxman]

LOL.... Wow, that looks..... just from the screenshot.... like it would be messy code....

You saw that just from the screenshot ?

Did you try running the application ?

On a side note, it took more time looking at the documentation than actually writing the code. It wasn't that fun to write, I just wanted to see if it would actually work.

[MacGyver]

I didn't compile it, but I did look through the source code briefly just now. It does look kind of..... involved.

[Mario F.]

Good one. Consoles are always fun with me. But I can guarantee you will have more if you give ncurses a shot.

Noticed you had a pretty bit of fun with exceptions You should probably drop most of them and replace with more traditional error checking methods. Or, better yet, since you are lerning C++ try to give them a little bit more of personality and create your own exception handling classes.

Also... consider declaring enums outside class definitions. It works very well if you couple that with namespaces.

I liked it overall. Small, organized and easy to understand code.

[foxman]

But I can guarantee you will have more if you give ncurses a shot..

Well I found the services provided by the Windows API fairly exhaustive. The only bad thing -- and the good one, too -- is that the most interesting stuff is fairly low-level. But since I have never worked with ncurses, I couldn't really tell.

Noticed you had a pretty bit of fun with exceptions You should probably drop most of them and replace with more traditional error checking methods. Or, better yet, since you are lerning C++ try to give them a little bit more of personality and create your own exception handling classes.

I do feel there's something not totally correct with the way I have used exception, but I'm not really sure what should I have done instead. I mean, in the 2 principal functions (Labyrinthe::Labyrinthe (loading the labyrint) and Jeu::Jeu(setting up the input and screen buffer)), there was quite a good amount of "special case" or "potential error" that I needed to check for the program not to crash, so... well, that's how I explain the fact there's a lot of "exception throwing places".

But thanks for the comments.