Once you have Eiffel Studio asking you about keeping or discarding
assertions again, you may want to consider a tactic that we use.
In our pre-production system, we have a need to three distinct EXEs:
1. AssertionlessâNo contracts at all.
2. PreconditionedâOnly preconditions for our code.
3. IntensiveâAll contracts.
The #2 option is the one of interest. In order to do this, we created a new
target and then turned on preconditions only (setting all others to False
for the target). Then, when we compile, we do so through the command line
process, handling the question of keep-or-discard to get #1 and #3, but
compile the preconditioned target as though we're doing "keep all", which
only ends up keeping the preconditions.
I think in this way, you could manage any number of EXEs with various
contract assertions turned on and off as needed by simply controlling which
contracts are turned on for the target.
On Wednesday, October 7, 2015 at 8:42:58 AM UTC-4, Colin Adams
Post by Colin Adams ***@gmail.com [eiffel_software]When first finalizing in EiffelStudio, there is a dialog that pops up and
asks you if you want to keep assertions or discard them. And an option to
never get asked again, and always discard assertions.
Of course, I always tick that last option.
But now, after many years, I have finally come across an instance when I
need to enable assertions in finalized mode. So how can I turn it back on
again?
[Non-text portions of this message have been removed]
------------------------------------
------------------------------------
------------------------------------------------------------------------
Eiffel Software
http://www.eiffel.com
Customer support: http://support.eiffel.com
User group: http://groups.eiffel.com/join
------------------------------------------------------------------------
------------------------------------
Yahoo Groups Links
[Non-text portions of this message have been removed]