 | | | Question regarding sh_int | Question regarding sh_int 2004-01-25 - By Cyhawk
Back
On my quest to find more vnums (as my world takes up 25,000 as it is,
adding new areas is a true pain, my hats off to erwin for the perl one
liner to automate this)
and looking for a few "unlimited vnum" snips, i wondered.. and tried to
come up with a simple solution on my own.
My solution, was to
#define sh_int int
in merc.h
Low and behold, it worked.. Now.. my question is..
What sort of backlash am i looking at here? Aside from the incressed memory
usage (which from what i see, is a whole .4% on a 256 meg machine)
Do i have any long term issues i need to address? Was this a completely
foolish idea from a newbie coder?
Now, as i understand it, sh_int was created as a short integer, for
memory/cpu considerations way back when i was still using my Atari ST
to surf around on gopher and BBSs, but with todays machines..
/begin_bloat_ware/ is it really nessecary to micromanage everything? /end/
Feel free to slap me silly if this is just utterly the wrong approch to the
issue at hand.
-Thri
--
ROM mailing list
ROM@(protected)
http://www.rom.org/cgi-bin/mailman/listinfo/rom
Earn $52 per hosting referral at Lunarpages.
|
|
|