Jump to content

  • Log In with Google      Sign In   
  • Create Account

Banner advertising on our site currently available from just $5!

1. Learn about the promo. 2. Sign up for GDNet+. 3. Set up your advert!


Member Since 10 Nov 2005
Offline Last Active Yesterday, 08:04 PM

Posts I've Made

In Topic: Your Death Song

06 April 2015 - 06:27 AM


Starting from 4:44. A full 1 minute and 15 seconds to die the most beautiful death ever. I might consider holding my breath for the duration.

In Topic: Can you boil eggs and pasta at the same time?

24 March 2015 - 05:34 PM


Eggs would get smashed in the washing machine.


Ever heard of pillows?


EDIT: never, ever, ever  tumble dry eggs.

In Topic: Can you boil eggs and pasta at the same time?

24 March 2015 - 09:04 AM

And this is why I prefer the GD Lounge to boredpanda.

In Topic: Recommend me a "classic RTS" mainly for offline skirmish gaming?

23 March 2015 - 01:18 AM

For single player, Warzone 2100 (it's free and has been greatly enhanced by a devout fanbase) and the Earth series. While I never really got into the Earth games, WZ2100 is one of my favorite games of all time - unit customization, several hundred research projects, a great atmosphere and really challenging gameplay, even if that is often caused by dated AI and pathing (they may have fixed some of these issues in the fan version, though - haven't played it in a while).

In Topic: Would you choose an engine based on it's coding style rather than it'...

19 March 2015 - 11:58 AM

I am a solo programmer, but I do read others' source code every now and then. I also have my own style, which isn't as set in stone as it should be.

The one thing I value above all, however, regardless of the coding style used, is clarity. Unless you are indeed reading code on the web, the type info part of a variable's name should be made moot by the IDE.

That being said, I do use it occasionally in interface-level code to differentiate between ambiguous types or when the type is non-trivial:

TEXTUREHANDLE smpTextureSamplerName
HANDLE thdThreadName
SharedPtr<wchar_t> wString

But not in places where the reader can tell the type with 99% certainty or, if they want to be 100% sure, they can casually hover over the variable name and the IDE does their work for them.

In other words, I can appreciate type information to stress or draw attention to an unexpected type, much like composers add accidentals in parentheses to speed up reading the sheet music if there's enough confusion surrounding the note that its sign may not be instantly clear.

Writing out every type every time a variable name is used is as overly verbose as adding an accidental before every note.