In the course of my work with the Chapel codebase I've noticed that there
are some bits of code that are only of interest to developers but they are
either always compiled (asserts) or their compilation is controlled by a
macro defined in a source file (tracing for the function disambiguation
process). In the first case code that isn't needed for a release build is
included in the binary, thereby making it slower and larger. In the second
case the distinction between a development build and a release build is
actually encoded in the repository.
Both of these issues could be addressed by using a configuration system
like CMake or autoconf that would set macros controlling the visibility of
development code. In addition, this could help with situations that arise
from developing Chapel with different compilers and library versions, like
the one we had with bswap.h.
Is there any interest in getting a configuration system rolled out for
Chapel?
- Chris
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers
