ZirconiumX wrote:
The Dutch G makes an English H sound. So it's pronounced Dorps-heck. It's hard to wrap the tongue around though.
As for the origin, I have friends in Flanders, which is Dutch speaking.
I wouldn't say it's similar to an H-sound in English; it's a much harder sound that doesn't actually exist in English - and you actually have to pronounce the r to get it right too .
On the other hand, the g is much softer in Flemish than it is in Dutch Dutch*, so perhaps that is closer.
*It seems a bit odd to render the distinction as "Flemish" and "Dutch", seeing as both are Dutch (neither is more correct than the other, although of course I would never admit that to my Flemish friends and relatives), but with a slightly different pronunciation and idiom.
I think you can make them from the CODE::Blocks GUI, (IIRC) in order to get gcc to create them on windows.
Or you can get the free MS compiler and it will make them because I do it all the time.
Taking ideas is not a vice, it is a virtue. We have another word for this. It is called learning.
But sharing ideas is an even greater virtue. We have another word for this. It is called teaching.
Taking ideas is not a vice, it is a virtue. We have another word for this. It is called learning.
But sharing ideas is an even greater virtue. We have another word for this. It is called teaching.
ZirconiumX wrote:So my chess program Dorpsgek crashes fairly often in games. To be expected, really - it's pretty new.
The problem is, despite my best efforts, I can't reproduce any of the crashes. They're all heisenbugs that disappear under GDB.
So what do people normally use as a method to debug problems that occur in games, but cannot be reproduced?
If you are running under Linux, enable core dumps, and when you get a crash, type "gdb progname corename" and you will magically be in the middle of the program at the instant it crashed...