Wrong, you'll also need to update quite a few of the libs(if you want it to work in vs2010 at least).
If you checked the developer preview; upgrading is a thing of the past. I wouldn't be too worried unless some project uses VC6.
But like I said, you'd have to break compatibility with older compilers - very minor edits; e.g, they're assuming the state of iterator 'i' exists out of scope.
Code:
if(kind)
{
// °°Àº°Ô ÀÖ´ÂÁö ã°í
for(int i=0; i<pPreLoadInfo->Count[ePreLoad_Monster]; i++)
if(kind == pPreLoadInfo->Kind[ePreLoad_Monster][i]) break;
// ¾øÀ¸¸é »õ·Î¿î ¸ó½ºÅÍ Ãß°¡
if(i == pPreLoadInfo->Count[ePreLoad_Monster])
{
pPreLoadInfo->Kind[ePreLoad_Monster][i] = kind;
++pPreLoadInfo->Count[ePreLoad_Monster];
//
if(pPreLoadInfo->Count[ePreLoad_Monster] >= MAX_KIND_PERMAP)
break;
}
}
This was a remnant of ages ago when compilers didn't play nice with standards. Then again, you shouldn't use said compilers.
Still shouldn't be too difficult though. Not really interested in using this now that its public though. Looking through the code, it doesn't look like eyasoft has improved too much since IRIS/Luna1. Oh well, still got a nice hshield lib dated December 2010.
Totally agree with that. Then again, if it ain't broke, don't fix it.
They really should've broken down their client into multiple libraries, since MSBuild can spread the load over separate threads.