Reply to Re: Blankety Blank
If you don't have an account, just leave the password field blank.
This is just in case anyone tries to compile in the future to learn and gets those errors...
Don't worry about the warnings, it will still compile. You'll get a ton of strcpy, sprintf, and fopen is deprecated warnings. Don't worry about those for now, unless you feel like changing each one to strcpy_s (not to mention the others) and adding an extrafield which is the size of the string. Either way, the new functions are better, but will take a lot of work to get them implemented. It might be better to use a String class or something instead.
The "default-int" warnings are because they are set to "const" and the "int" was understood at the time. After all of those enter "const int" where "const" is. Don't do a "replace all" because there are a few that are "const char" and one other that is correct and will break if you use "replace all"...
After you correct all of those errors, the next ones are for loops that have the int in the wrong scope so it creates a ton of other errors. look for the next error and the first warning before it, and it should be something about "k" being a pic_info. That should really be an int. Go to the next for loop up and take "int k" and replace it with just "k" and right above the for loop put "int k;" so that it's scope will cover the next for loop. I would say to just put "int k" in the next for loop, but it's used again, so don't do that.
You will have to do this in the functions kill_all_scripts, kill_all_scripts_for_real, load_script, kill_returning_stuff (it's an "i" in this one), playbank (i), and process_item (i).
Actually if you just go to each of those functions to the first for loop and pull the integer initialization that might save you the time of finding the for loops.
-- And that's it. Compile with the warnings (it should ignore them and build anyway, but if you have to change a setting do so) and it should work fine. To get it to run after you have the executable, you will have to load a mod first though...
Don't worry about the warnings, it will still compile. You'll get a ton of strcpy, sprintf, and fopen is deprecated warnings. Don't worry about those for now, unless you feel like changing each one to strcpy_s (not to mention the others) and adding an extrafield which is the size of the string. Either way, the new functions are better, but will take a lot of work to get them implemented. It might be better to use a String class or something instead.
The "default-int" warnings are because they are set to "const" and the "int" was understood at the time. After all of those enter "const int" where "const" is. Don't do a "replace all" because there are a few that are "const char" and one other that is correct and will break if you use "replace all"...
After you correct all of those errors, the next ones are for loops that have the int in the wrong scope so it creates a ton of other errors. look for the next error and the first warning before it, and it should be something about "k" being a pic_info. That should really be an int. Go to the next for loop up and take "int k" and replace it with just "k" and right above the for loop put "int k;" so that it's scope will cover the next for loop. I would say to just put "int k" in the next for loop, but it's used again, so don't do that.
You will have to do this in the functions kill_all_scripts, kill_all_scripts_for_real, load_script, kill_returning_stuff (it's an "i" in this one), playbank (i), and process_item (i).
Actually if you just go to each of those functions to the first for loop and pull the integer initialization that might save you the time of finding the for loops.
-- And that's it. Compile with the warnings (it should ignore them and build anyway, but if you have to change a setting do so) and it should work fine. To get it to run after you have the executable, you will have to load a mod first though...
