Ran them both in compatibility mode for Windows 7, and ran as admin as well. Both discs are in very good condition and both versions of the game installed quickly with no issues. I noticed that the Gold Pack is on sale, but wanted to check to see if my old discs still worked. The rest is up to you.Originally posted by Lord_of_the_Bacon:So, I have the original EaW, and FoC discs from way back when. It gets the job done, it’s easy to understand, and it empowers the programmer to do the right thing when the program fails. “if … err != nil” is something you’ll probably type if you write go. When I write Go code, error handling is the one thing I never worry about, because errors themselves are a central aspect of every function I write, giving me full control in how I handle them safely, in a readable manner, and responsibly. If I could summarize the most important pieces of advice I’ve received regarding writing idiomatic error handling in Go:Īdd stack traces when your errors are actionable to developersĭo something with your returned errors, don’t just bubble them up to main, log them, and forget them Which print out a stack trace along with the human-readable error chain you created through your code. Wrapf ( err, "could not save user with email %s", email ) On top of this, if you want to also attach a stack trace to your functions, you can utilize the fantastic /pkg/errors library, giving you functions such as:Įrrors.
This sort of error chaining using fmt.Errorf("something went wrong: %w", err) makes it trivial to build awesome error messages that can tell you exactly what went wrong based on how you defined it. The beauty of the code above is that each of these errors are completely namespaced by their respective function, are informative, and only handle responsibility for what they are aware of. Func getUserFromDB () ( * User, error )
0 kommentar(er)
