Saturday, September 02, 2006

void

This post is for anyone who got the wrong impression of void being nasty. It's a programming paradigm from the C language. Computing languages all allow data storage, more advanced (low-level) languages get very specific about storage in terms of the size and interpretation of the storage. Typical storage is for something like an integer, integers are good, but can only hold whole numbers, float for instance can hold fractions, and so on.

Suffice to say there are many storage types all for different tasks, it is even possible to create storage structures or containers, which can act as holders for a few storage locations all in one. That brings me to void, it is a really really powerfull storage, because it can store anything depending on how you use it. It is possible for a void to store a integer, a float or even a structured container, very usefull if you ask me.
The depending bit is important here. As storage locations go, void is like a great big piece of white paper of unlimited size, without some control that can cause problems, very nasty problems. Loosing track of data in a computing system is never a good thing, pretty much equivalent to the 'where did my file go?' question. That is the nasty part :-)

No comments: