Mars Saxman write:
we will never get a proper assert implementation simply because
they wish to enforce a particular development style upon us for
our own good.
This discussion is a pretty good demonstration of the idea that
different developers, and even different projects, need an assert
system to do different things. I suspect that a one-size-fits-all
assert system built into the RB framework would cause more problems
than it would solve.
It would not cause more problems since people would not be forced
to use it if they did not want to. In a previous email I described
how you could easily go about to implement this to allow for
diversity of implementations. Other people have suggested
implementing macro capabilities to cover this, so there
are several ways to solve this problem.
Mars, do you recognize the need to have a zero foot print assert
without having to resort to #if around the asserts? If you really
want to serve our needs, then come up with a solution that gives
us that.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
