From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Any Suggestion How To Accomplish A Debug Macro? Date: Tue, 30 Dec 2014 18:21:50 +0000 Organization: A noiseless patient Spider Message-ID: References: <82329c51-2302-468b-a5d0-3bfab3999014@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="da19c0dc8eec016b1dd8c302a793eb7c"; logging-data="28586"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/60oC2kvNzp0bUAFCtBJttjDPoF2Smzl4=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (darwin) Cancel-Lock: sha1:sxpEM8EJQ6ngFNL/xfh7WbMoac8= sha1:pWg9iV3Ra/Q/FadKejT/jzvLIxQ= Xref: news.eternal-september.org comp.lang.ada:24295 Date: 2014-12-30T18:21:50+00:00 List-Id: sbelmont700@gmail.com writes: > TWYF, FWYT. Having the compiler cull a bunch of your code, especially > such I/O heavy code, and expecting it to work the same in the release > is a bad idea (though there are better solutions than an if statement, > e.g. observer pattern). We did desktop testing (mainly functional, some timing) on Windows for deployment on powerpc-wrs-vxworks. On-target validation & verification was hugely simplified, and I don't recall any instances of on-target failures that were down to compilation differences. We retained the same logging in the two environments; on the host, via a low-priority task to standard output; on the target, via ethernet to a logging computer. So the Ada code of the subsystem under test wasn't altered.