Like everyone said, change the int to a long. Now... here's some suggestions on bug catching other than compiler errors and warnings. Note the vnum fields you changed ch->in_room->vnum (the room data, etc).. and grep through the files for all those occurances... then go through each of those and change the %d to %ld. Once you get it compiled you'll know when you access a field you didn't change because you'll crash and gdb should plainly show you the problem. I did this around a year ago by hand and though it took a long time, it really wasn't that bad. Just in case though, back up your code :)
Rhien. -----Original Message----- From: Jason Gauthier [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 21, 2003 8:56 PM To: '[email protected]' Subject: RE: Vnum Limitations unsigned longs are 4billion positive. Longs are -2billion to 2billion. Also, changing the typedef is not sufficient. You will change things that shouldn't be changed to longs, and you will not get them all. The *only* fool proof way to expand your vnums is to go over your code with a fine-toothed comb and change the 'int's to 'long's. > -----Original Message----- > From: Boh-Ahz [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 21, 2003 8:37 PM > To: 'Shaun Mcbride'; [email protected] > Subject: RE: Vnum Limitations > > > If I'm remembering right, you should just be able to change > the 'typedef' of sh_int (all vnums are sh_int's) to be an int > rather than short int. For most modern systems, both ints > and longs are 32 bits, which should give you more than enough > space (4 billion plus I think). Oh, and by changing the > typdef to just int (rather than the short int), I don't think > you would need to change the string formatting either. > > Boh-Ahz > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Shaun > > Mcbride > > Sent: Tuesday, January 21, 2003 5:41 PM > > To: [email protected] > > Subject: Vnum Limitations > > > > Anyone know where I can get the fix for the vnum limitations? The > search > > feature on the archives seems to be broke. > > > > > > > > > > > > -- > > ROM mailing list > > [email protected] > > http://www.rom.org/cgi-bin/mailman/listinfo/rom > > > -- > ROM mailing list > [email protected] > http://www.rom.org/cgi-bin/mailman/listinfo/rom > -- ROM mailing list [email protected] http://www.rom.org/cgi-bin/mailman/listinfo/rom
