PS: Static Investigation equipment like FindBugs and PMD detects the usage of magic numbers in the code and suggests the refactoring.
If by STL you imply only the template part of the C++ Normal Library, then it's flawlessly feasible to put into action it with no "magic".
For future google visitors: A further solution is placing the %MAGIC% enviroment variable inside the techniques placing to point to the magic file, for me it absolutely was:
In addition they continually use names that you're not allowed to use. For example, template parameters are generally named anything like _Type, which, since it starts using an underscore accompanied by a money letter, is reserved for the implementation
My code is filled with worldwide constants like HzPerMHz and msecPerSecond. These will never alter, Nevertheless they make the this means clearer, and provide some defense against typos.
Distinction this with magic constants which happen to be the results of naive people today thinking that just mainly because they take out the particular quantities from their code, they might improve:
It really is certainly a distinct segment region acquire in and for this reason Employment are couple and far between. As it is interpreted you will find seriously no bugs to produce. It will operate with many databases/connections concurrently but there is a huge memory and processing hit. Downsides :
Like gbjbaanb accurately mentioned, the STL can be executed in basic C++, with no relying on any kind of compiler "magic".
While in the unusual situations in which I discover the need to use these types of Magic Figures, I set them to be a const in my code, and doc why They can be utilized, how they work, and wherever they came from.
For example, you might have a magic number of 0x12345678. If you see that magic number, it's a good guess you might be looking at a file of the proper structure. If the thing is, Conversely, 0x78563412, it is a truthful guess that you are observing an endian-swapped Edition of the identical file format.
It is strictly this: Speedy, Rapidly, but highly-priced and rigid in what it will let you do. It really works with a tick tack toe like matrix. Dropping in instructions into the assorted sections decides when they're run.
A quick Test of your magic quantity just before processing the file or facts structure makes it possible for a person to sign errors early, as opposed to schlep every one of the way as a Lisa result of potentially lengthy processing to be able to announce the input was comprehensive balderdash.
I do think static ultimate constants are overkill if you're making use of them in a single approach. A remaining variable declared at the very best of the tactic is much more readable IMHO.
C++0x normally takes it a single stage further and gives versions of those form traits that truly get the job done accurately in all instances. And that can only be finished by some unspecified kind of compiler assistance.