I have now rewritten my Norman interpreter three times. It is now, so far, this iteration is working great. The previous attempt was riddled with strange silent crashes.
Java would run, reading through the game definition files, performing trimming and substrings and other String parsing methods. Then unexpectedly Java would just crash. No error message, nothing. I spent hours adding output messages all throughout the code, but was never able to pinpoint the source of Java's sudden death.
After giving myself numerous concussions on my desk I decided to scrap the interpreter and rebuild it. This time around I filled every block of logic with try/catches and more comprehensive output messages. And I improved how it processed the files.
So far so good. we'll see how it does as I convert more of my game definitions to Norman Notation.
I would really like to know what methods are prone to causing Java to quietly and horribly die. If this ever comes up again I suppose I'll be spending days and days trying to solve the mysterious mystery.
Java would run, reading through the game definition files, performing trimming and substrings and other String parsing methods. Then unexpectedly Java would just crash. No error message, nothing. I spent hours adding output messages all throughout the code, but was never able to pinpoint the source of Java's sudden death.
After giving myself numerous concussions on my desk I decided to scrap the interpreter and rebuild it. This time around I filled every block of logic with try/catches and more comprehensive output messages. And I improved how it processed the files.
So far so good. we'll see how it does as I convert more of my game definitions to Norman Notation.
I would really like to know what methods are prone to causing Java to quietly and horribly die. If this ever comes up again I suppose I'll be spending days and days trying to solve the mysterious mystery.
No comments:
Post a Comment