On Wed, 2008-04-16 at 09:47 +0100, Tim Bunce wrote: > I agree with Geoffrey that optimized builds should be the default.
Thank you! > Developers working on parrot (wanting unoptimized/debug quick builds) > would just need to set an env var in their .profile, for example, and > carry on as now. No changes in their procedures, and no changes in the > docs (other than to mention the env var). The only issue here is that in the past the optimizers have had a number of bugs (presumably because the optimized builds were getting used so rarely). If the developers never use optimized builds, but we ship them to end users, then A) each monthly release will be buggier for end users than the developers think it is, and B) we'll get confusion when attempting to recreate reported bugs. That's part of why I recommended the more complex arrangement, in which the two parrot variants are both built and self-documenting, rather than only one being built which is magically different for developers and end users. I understand Tim's concern that this is a complex arrangement, so here's a compromise: can we at least agree that the pre-release testing should include running the full test suite against both the debug and optimized builds, and that there should be some easy way for a developer to choose to run the test suite using either or both builds at will? -'f
