Approve against return false?

Question

bool fn()
{
  if(something bad happen)
     return false;
  ..
}


void gn()
{
  assert(something == true);
  ..

}

When I write a function in production code, how should I choose?

Answer 1

Assert, at least in .NET, is used for testing in the first place. Its specific use is presented briefly here :

An assertion is best used to verify a condition only if the following conditions are true:

* the condition should never be false if the code is correct,
* the condition is not so trivial so as to obviously be always true, and
* the condition is in some sense internal to a body of software.

In production code, I would recommend the first method; or try/catchif "something bad" is never expected; if this is an exceptional condition.

, ( ), Assert .

; . .

Answer 2

, , " - " = - ...

Answer 3

assert , , ( , ). - , , .

-, ( ), (, invaid , , ), / (, ,...).

Answer 4

"return false" GuardClause - :

... [G] uard , . , , , . "" EwDijkstra .

, BouncerPattern.

, , . assert, .

, . . unit test. ( ...), , , .

" ", , , . , " " .

Answer 5

IMHO, assert , - (). , .

false , , .

Answer 6

assert, - , . :

int div( int a, int b ) {
  assert( b != 0 );
  return a / b;
}

, div() . , .

if()... return, , . , - .

Answer 7

. (.. , - ). , - , , - . . , , .

Answer 8

- , - . , fn() , . . , , , . , gn , - , , eithers if , . , , , .

.

Answer 9

/ .

(.. ). , .

, , , , , .

" " ( b/c ), , , .

Answer 10

, . , , , , , - . false , .

Answer 11

, - . : . , . . Eiffel.

() , StrinToIntegerDef (, ), , Integer.

false , .

, , assert (condition, message), .

Also, if there are several possibilities for rejection, return some enumeration values ​​instead of false.

Answer 12

Use the statements for the function mandate preconditions (conditions that must be true if the function must have any value).