On Tue, 1 Apr 2003, Dennis wrote: > You're going the wrong way. Going through and removing the consts will > fix your warnings, but it works against the point of having the const > there in the first place. > > It looks like you've figured out what the problem is: going from a > const pointer to a non-const pointer. But you're working backwards. > Instead of removing the const from the original pointer, and working > backwards from there, you should be going the other way. Go to the > lines causing the original warnings, and add const to those pointers. >
> > Fixing those specific lines may cause more warnings, similar to what > you're seeing when taking the const off. Just work through them > until you fix them all. > > > Dennis Thanks again for all of the help! I finally have a nice, clean, error-less compile once again :) *cheers* Maybe once I finish bug fixing, I should tar & gunzip it all up to distribute to people that can figure out how it all works.. those unlimited bits can be confusing! Now to go fry my last brain cell on trying to fix the in-game unlim bit/affect problem.. --- RogueDragon @ A Merging of Fates MUD telnet://mud.merging.org:5454 icq: 2072355 (inactive atm), yim: roguedragon, aim: roguedragon69 --- Windows - Where do you want to go today? Linux - Where do you want to go tomorrow? FreeBSD - When are they going to catch up?
