Jump to content

  • Log In with Google      Sign In   
  • Create Account


Member Since 09 Dec 2005
Offline Last Active Yesterday, 03:25 PM

Posts I've Made

In Topic: Keyboard vs Mouse for in roguelikes and in general

24 January 2015 - 07:55 AM

(1) For a good evaluation of How Not To Do Keyboard Right and How Not To Integrate a Mouse in a roguelike play Dwarf Fortress for a few hours (or days, or...). I discovered, for example, that I can not play that game on any of my laptops because certain screens require keys on the numeric keypad (which none of my laptops have without using an external keyboard) and some actions require using the mousewheel (which is not present on my clickpad).

(2) This is the 21st century. Consider that most computers do not have a keyboard or a mouse.  Try designing a UI so it can be useful with or without a keyboard and with or without a multi-button mouse (eg. only a touchscreen, or maybe somatic feedback while using your Holograph goggles).

In Topic: Best Computer Type for Game Dev?

23 January 2015 - 05:52 AM

The most important things are display, keyboard, and RAM in that order). You spend all your time looking at the screen, caressing the keyboard, and waiting for builds. At least 8 MB RAM; the rest requires some hands-on (and eyes-on) testing and is a matter of personal preference.

In Topic: Encapsulation through anonymous namespaces

22 January 2015 - 07:03 AM

BTW, it's the same as:

Not entirely: there's an important difference between names with static linkage and names with extern linkage. For example, templates can only be instantiated with names of extern linkage. Names with extern linkage get involved in link-time resolution, names with static linkage do not (so giving things static linkage where possible can speed up build times, sometimes remarkably).

Names at namespace level (including the :: namespace and the anonymous namespaces) by default have extern linkage. Adding the 'static' keyword gives them static linkage instead.

Still, it is the traditional C way of encapsulating things, used since the early 1970s. There are worse things to reinvent.

In Topic: c++ Heap corruption w/ std::vector

20 January 2015 - 10:24 AM

What is the smallest, simplest program that reproduces the error for you? The code you posted contains no errors, we can't guess at the code you did not post.

In Topic: why C++?

19 January 2015 - 08:29 AM

The answer is at your fingertips.