Thread: void keyword

I find that it's best to return a value to indicate success, so that the code that called the function knows how to proceed. This is the function template I use:

Code:

BOOL DoSomething()
{
    BOOL bSuccess=false;

    //once the function has successfully completed its task:
    bSuccess=true;

    return bSuccess;
}

This can make debugging easier by allowing you to quickly determine which functions cause the error. Thus, development is sped up.

yeah, for some reason I cringe when i see void anything... not just void main... i don't like the void keyword unless it's in the parameters:

Code:

bool somefunction(void);

Lol, what are you, a C programmer ;-)

You can also use try..catch blocks if your function doesnt return anything:

Code:

try
{
somefunction();
}
catch (const Error&)
{

//...
}
//...
void somefunction()
{
throw (Error);
}

Although my syntax might not be right since I don't have a compiler with me

Originally posted by JaWiB
Although my syntax might not be right since I don't have a compiler with me

Error would have to be a valid type obviously (it'll most likely be a typedef) but it looks all right.

Originally posted by major_small
yeah, for some reason I cringe when i see void anything... not just void main... i don't like the void keyword unless it's in the parameters:

Code:

bool somefunction(void);

You blokes are funny. If I have something, like a print method, I would cringe doing something like:

Code:

bool blah::print() const {
  cout << data << endl;
  return true;
}

I don't like the idea of a function returning the same value every time it's called. I mean if it is never going to be checked, then it has no purpose, it has no "why". But of course that's just me.

I don't like the idea of a function returning the same value every time it's called.

Yeah it seems kind of stupid. However, that is not what occurs in my functions. I return bSuccess=true when the function is successful. I return bSuccess=false when the function is not successful. I always check the return values from my functions. Thus, it is very useful.

You blokes are funny.

Being pedantic, and sticking to the standard, is a good character trait. It (helps) to ensure perfection, and reduces development time. Having a good programming ethic will pay off when you are developing something on a huge scale, because you will avoid stupid petty small errors.

I'm not saying that BOOL DoSomething() is going to destroy your computer, but sticking to the standard, and writing 'void' where there are no parameters, will encourage you to write correct code ALL the time.

Code:

bool blah::print() const {
  cout << data << endl;
  return true;
}

In this example, why not return the value from cout itself, that way the caller can verify that cout actually worked.

For example:

Code:

bool print(char *data, ofstream &os) {
  return os << data << endl;
}