<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Hi Axel, Hi All,<div><br class="webkit-block-placeholder"></div><div>with a today commit we have the necessary platform for specifying things in cp2k as</div><div>ready to be released or still in a development version.</div><div>Each section/keyword of the input has an additional marker (supported_feature), by default</div><div>set to .FALSE. and in case that section/keyword is considered sufficiently tested to be released</div><div>it can be set to .TRUE. in the source.</div><div><br class="webkit-block-placeholder"></div><div>CP2K can now be compiled with a prepocessor flag: -D__RELEASE_VERSION.</div><div>Whenever producing a release version and one tried to access keywords/sections not upgraded</div><div>as being supported_features cp2k stops with an error message. </div><div>I also introduced, as you suggested Axel, the "ENABLE_UNSUPPORTED_FEATURE" keyword in &GLOBAL.</div><div>In case it is specified and in case one runs a release version the program prints some warning messages </div><div>but the calculation continues exactly as for a development version.</div><div>For development version no check is performed whether a keyword is supported or not.</div><div><br class="webkit-block-placeholder"></div><div>Now there's the fun part of the game: decide which keywords/sections can be considered supported.</div><div>I can do that for part of the input (but only in my spare time, I did it only for few keywords to debug the </div><div>today commit).. If one wants to contribute please just send me the proper patches for the keywords he analyzed.</div><div><br class="webkit-block-placeholder"></div><div>The other thing to do is to provide for the platforms for which we want to support the release the proper</div><div>arch files with the extension .release (an arch file like sopt in which the -D__RELEASE_VERSION is added).</div><div>In this case one can compile the release just typing "make release" or something similar (I didn't add any arch file at the</div><div>moment)..</div><div><br class="webkit-block-placeholder"></div><div>The next thing to do is to mark with different color supported/non-supported keyword on the on-line reference manual (still</div><div>didn't do that).</div><div><br class="webkit-block-placeholder"></div><div>Cheers,</div><div>Teo</div><div><br><div><div>On 5 Jan 2008, at 22:31, Axel wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">as written before, the most important decision would be to</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">identify features, that should be labeled as supported. i would</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">recommend to not remove anything from the release version, but</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">rather add a flag to check clear supported features. the input could</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">have a keyword (in &GLOBAL) ENABLE_UNSUPPORTED_FEATURES which</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">would be set to false by default in releases and true in developement</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">versions. that would make maintenance easier and every developer of</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">a subsystem can decide on a fine grained level whether a feature</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">is production ready or not.</font></p> </blockquote></div><br></div></body></html>