Re: Trick to prevent conversion
"Victor Bazarov" <v.Abazarov@comAcast.net> wrote in news:fm8mn0$8gr$1
@news.datemas.de:
class Processor {
public:
unsigned GetCurrentProcess(void);
unsigned GetCurrentThread(void);
If you can, perhaps you would get in the habit of omitting 'void'
for a function with no arguments. I know I'd appreciate it because
your code would be easier to read and understand.
I hadn't even realised I'd written "void"; I program in C and it just
feels more natural to me, more verbose.
Also, it seems that those functions should perhaps be 'const'. If
they don't change anything in 'Processor', of course.
Ah yes, of course, I'm a little rusty.
Of course, this does the trick. But I'm wondering if there's a more
elegant way of doing it? What other methods are there for making
types
incompatible with each other?
I have a list box on a dialog box. The list box contains items, and each
item has an index. First item = 0, second item = 1, third item = 3, you
get the idea.
I have a function that returns the text of one of those items:
char const *GetItemText(unsigned const i);
"unsigned" is definitely a natural choice for this, because the index is
nothing more than an integer. However, I've been using:
struct ItemHandle { unsigned i; };
so that the programmer definitely won't supply the function with a
different kind of index. I've at least three kinds of closely-related-
but-different indices floating around in the same function, and so I
need some extra reassurance that the programmer won't mix them up. Hence
the want for types that won't convert to each other.
I've already got a solution that works; maybe I should just leave it at
that.
--
Tom1s # hilidhe