This is the first of a series of posts, I want to go over some of the groundwork of what it takes to make exceptions localizable into other languages. Nothing new here, but just want to explain clearly the requirements of a localizable exception messages.
Tag Archives: code style
Still reviewing that code base and finding more bad patterns for use of constants, this time for error messages. This is another “don’t do this” post. Read the rest of this entry »
Software will always increase in amount and size, and that includes not only things that are needed, but unneeded things as well. Unless you fight diligently against it, code will tend to get more and more cluttered. Read the rest of this entry »
A “best practice” is a heuristic which is used to guide early stages of a project, in order to set some patterns. When should you use them? More important: when are you justified in ignoring a best practice? Read the rest of this entry »
An exception is a message from the system to the user about something that the program can not handle. There are a couple of main categories of exceptions: environmental and program logic. They warrant quite different treatment. Read the rest of this entry »
Someone long ago set a pattern that all members should have a getter and setter method. Some are persuaded that this is OO and this is encapsulation, so a lot of inexperienced programmers do this by default. But this is a problem. Read the rest of this entry »