return const and assert

[alexhong2001]

When to return a const, from either a member function of a class or
non-member?

Is assert() only executed in debug mode but skipped in release mode? I
don't see much usage of "assert()." Am I missing its importance?

Thanks for your comments!

[Victor Bazarov]

"alexhong20 01" <al**********@h otmail.com> wrote...

When to return a const, from either a member function of a class or
non-member?
When returning by value, 'const' really isn't of any use. It's
basically like adding 'const' when passing by value: means almost
nothing.
Is assert() only executed in debug mode but skipped in release mode?
Using your terminology, yes.
I
don't see much usage of "assert()." Am I missing its importance?

Probably. 'assert' is a debugging tool for code where you don't
want to have a run-time check once you cleaned everything up.

V

[Phlip]

alexhong2001 wrote:

When to return a const, from either a member function of a class or
non-member?
Call these "top level const":

void function1(int const q);
int const function2();

Don't do that. The 'const' has no meaning to the calling code, because both
values pass by copy. The qualification (const, non-const, volatile,
non-volatile) of the copy are irrelevant.

But do this:

class foo {
int bar;
public:
int const & getBar() { return bar; }
};

Do that so those who access foo::bar cannot change its value. The /Effective
C++/ books cover this.
Is assert() only executed in debug mode but skipped in release mode?
If your implementation' s "release mode" defines NDEBUG, then assert() goes
away. But this newsgroup is not qualified to discuss "release mode", because
the configurations that your implementation provides by default are
implementation-specific. Questions about "release mode" will get the best
answers on your compiler's newsgroup.
I don't see much usage of "assert()." Am I missing its importance?

Assert() is the most important function in the whole programming industry.
You won't see it much in the tutorial code. But consider this simple
example:

int main()
{

Source aSource("a b\nc, d");

string
token = aSource.pullNex tToken(); assert("a" == token);
token = aSource.pullNex tToken(); assert("b" == token);
token = aSource.pullNex tToken(); assert("c" == token);
token = aSource.pullNex tToken(); assert("d" == token);
token = aSource.pullNex tToken(); assert("" == token);
// EOT!
}

Passing the test requires objects of type Source to parse strings, ignoring
spaces and commas. If you add assertions to test cases like this, get them
to fail, and then edit your source to make the tests pass, you can grow
programs of any size and complexity, without the need to ever operate your
debugger. Run the tests after every 1~10 edits, and only perform the kinds
of edits that immediately return a program to a state where all the tests
still pass.

That technique trades long hours debugging for short minutes writing tests.

--
Phlip
http://www.xpsd.org/cgi-bin/wiki?Tes...UserInterfaces

[lilburne]

alexhong2001 wrote:

I don't see much usage of "assert()." Am I missing its importance?

This is a function to determine the number of steps required to
approximate the portion of a curve, between parametric values t_start
and t_end, to a given tolerance.

int Curve::num_step s(
double t_start,
double t_end,
double eps
) const
{
CHECKVALID_CLAS S;
ASSERT_STATE(!i nvalid(),"Curve ::num_steps");
ASSERT_STATE(!i nfinite(),"Curv e::num_steps");
ASSERT_ARGUMENT (eps>0.0,"Curve ::num_steps");
ASSERT_ARGUMENT (t_min()<=t_sta rt, "Curve::num_ste ps");
ASSERT_ARGUMENT (t_end>=t_start , "Curve::num_ste ps");
ASSERT_ARGUMENT (t_end<=t_max() , "Curve::num_ste ps");

// compute the number of spans to match given tolerance.
const int nspans = utMath::ceiling ((t_end - t_start) *
utMath::sqrt(de riv2_max(t_star t,t_end)/(8.0*eps)));
// make sure we have at least one span.
return nspans<1 ? 1 : nspans;
}

As you can see assertions of one form or another dominate the function.
Asserts help you to build reliable systems, detect and zero in on bugs
quickly, and provide the mechanism for writing automatic tests.

[EventHelix.com]

> Is assert() only executed in debug mode but skipped in release mode? I

don't see much usage of "assert()." Am I missing its importance?

Checkout the following article:

http://www.eventhelix.com/RealtimeMa...y_contract.htm

Sandeep
--
http://www.EventHelix.com/EventStudio
EventStudio 2.0 - System Architecture Design CASE Tool