One of the nice things of modern IDE’s are: they offer many extras for free. Many times it is related to programming and coding. But I love as well the ones which makes things easier and better which is not directly related to the executed code. One thing Eclipse offers is an on-the-fly spell-checking, similar to Microsoft Word:
Hovering over the text offers me to correct the flagged error:
But wait: is that example not spelled correctly?
And indeed, Eclipse offers to customize the spell checking. The option page is in the Windows > Preferences > General > Editors > Text Editors > Spelling page:
‘Initialization’ vs. ‘Initialisation’: that’s an ‘English US’ vs. English UK’ thing, and is easily changed. And I prefer the US English:
In later Eclipse versions (.e.g. Oxygen or Photon), make sure that the ‘C/C++ spelling engine’ is selected and configured:
With this, everything is ok now:
💡 After changing the platform dictionary, it usually takes a few minutes until the sources are checked again.
But what if Eclipse does not know a word? Then it offers to add it to a dictionary:
If I do not have a user dictionary yet, it will prompt a dialog:
If pressing ‘Yes’, it will prompt the settings page from above where I can specify my user dictionary file:
The user dictionary is a normal text file with one word on each line. That makes it easy to edit and to have it in a version control system.
💡 I have one common dictionary file for all my workspaces. But of course it is possible to have different dictionaries per workspace, as the settings are per workspace too.
I feel having reasonable spelled comments in the sources is just something an engineer should care about. And the Eclipse spelling engine does not have to be as good as the one in MS Word (which is pretty good in my view). But for making sources better something like correctly spelled comments is a plus. But only if the code works like a charm
Happy Spelling 🙂