![]() |
|
Java: Windows terminal isn't updating classes? - Printable Version +- Southperry.net (https://www.southperry.net) +-- Forum: Social (https://www.southperry.net/forumdisplay.php?fid=14) +--- Forum: Rubik's Cube (https://www.southperry.net/forumdisplay.php?fid=58) +--- Thread: Java: Windows terminal isn't updating classes? (/showthread.php?tid=62140) |
Java: Windows terminal isn't updating classes? - Jedward - 2013-02-04 Alright. This isn't as much of a code problem as it is a Windows problem. I'm using two machines at this very moment: One Linux and one Windows. I suppose that's irrelevant, but still. OK, I put the source files for my program on both machines and am trying to run them through the command terminal. Linux is running fine. It's busy sorting through a million integers right now. >_> Windows... isn't. Compiling the source code doesn't update the class definitions for some reason, even when clearing all source code files from the folder I was using. What happens is that when I run the class (here, Assign1), it's running old code that I'd compiled before completely finishing my file. How I know is that it's outputting test strings that I'd removed since then. Are the class definitions saved somewhere else besides the directory of the source code? Java: Windows terminal isn't updating classes? - Marksman Bryan - 2013-02-04 outFile doesn't contain anything/doesn't have a proper directory. what are you passing to printArray as outFile? Java: Windows terminal isn't updating classes? - Jedward - 2013-02-04 Old problem Wrote:Okay, so I have a method that writes the content of an integer array to a file, one per line. This is part of a bigger class, but I can confirm that everything works except for this last method. outFile is a string. Of course. Fixed it: string wasn't being initialized correctly and was returning a null value. See post 1 for new problem. Java: Windows terminal isn't updating classes? - Marksman Bryan - 2013-02-04 Jedward Wrote:A string. ... well, obviously The null pointer exception on that line means you didn't pass it a proper file directory. It had nowhere to create a FileWriter. I was asking what that string was. but you fixed it, so that's good. |