frustrating crash bug

[Pete Mack]

It's fixed, I think. I left a few scattered ')' characters around.

[will_asher]

You need two more open parenthesis at the beginning. (I don't really know how to write original code, but I know how to count parenthesis..).
Now your 'in_bounds_fully' works.
Thanks

[Nick]

I do a lot of things that way actually. I wouldn't know how to do it from scratch without help, so I just copy it from something similar and tweak it.

This is a very good way to learn, rather than trying to do everything from scratch and then giving up.

[PaulBlay]

Which brings us to the question: why are there two macros where one will serve?

Because it's easier to follow.

Sometimes I think it's more important that code is easy to understand than efficient. Of course "easy to understand" depends heavily on the person looking at it.

[will_asher]

I've quickly gotten to like this Visual C++ debugger a lot. When it finds a bug, it actually lets you know whats wrong, unlike my old compiler.

[will_asher]

So I was about to send DJA1098 to pav to post on oook, but I copied DaJAngband to my other computer and it wouldn't run. It gave me a message that said, "The application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem."
anyone know what this means?

[PaulBlay]

It gave me a message that said, "The application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem."
anyone know what this means?

I think that means it's a "Debug" compile not a "Release" compile.

See here for how to do a release compile.

(You just need to notice the "Set 'configuration' to "Release"." and optionally "Type "/DWINDOWS /DNDEBUG" into the Command line. " bits)

[Pete Mack]

It probably means you compiled in /Debug mode, but you don't have the Debug system libraries installed on your other machine. VC expects you to distribute only /Release builds.

[will_asher]

..oops, okay thanks

[will_asher]

I set configuration to release, but it still gives me the same error when I copy it to my other computer.

EDIT: nevermind, I just re-compiled with my old compiler. I guess it's still good for something.

unrelated PS: the rephial wiki isn't working

[Pete Mack]

You are absolutely sure you copied the right executable? (The one from src/Release--the other ones may or may not be correct.) Also, what exactly does it say for the linker options? (Does it say winmm.lib, or winmm.dll, etc?)

[will_asher]

Just a minute ago I found a copy of my DaJAngband debug folder in my "My Documents" folder. I guess for some reason Visual C++ must've created a copy there and was putting the new executible in a completely unexpected place. That's probably what was wrong.
(It does say winmm.lib in the linker options).

[will_asher]

<serious thread necromancy>

I finally got VC++ to install on this computer. yay.

I am reusing this thread because I'm using Paul Blay's instructions on page 2 of this thread for compiling in VC++ (and I'm also trying to fix a crash bug again)

When compiling the game (after getting rid of my errors in the code which didn't comply with VC++ standards), I'm getting these errors which I don't know what they mean, any help?

fatal error CVT1100: duplicate resource. type:MENU, name:ANGBAND, language:0x0409 CVTRES

fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt DaJAngband130

[Pete Mack]

Bing, like google, is your friend:

http://msdn.microsoft.com/en-us/library/3k67zd6z(VS.71).aspx

Not sure about the COFF failure, but one thing at a time.

[will_asher]

Okay got it to build. I had included the .rc file which was created by DevC++, so I had two .rc files and that apparently messed things up.

PS: This is weird. I found a bug that happens when compiling with VC++, but completely dissapears if I compile with DEVC++