On Wednesday 10 October 2007, Nicholas Nethercote wrote: > On Mon, 8 Oct 2007, Dirk Mueller wrote: > > >> Tools that required big core changes would be less likely to be accepted, > >> although it would be decided on a case-by-case basis. > > > > how do you think should this look like? accept core changes in an #ifdef? > > accept core changes as long as they can not affect any of the > > non-experimental tools? Delay addition of an experimental plugin until it > > doesn't require core changes? > > #ifdefs are a bad idea, IMO. The other two guidelines are possibilities.
Yes. FWIW, I am fine with branches. IMHO it is good to have a central place where experimental tools (and according core changes) are available. This way, the chance is higher that a new developer will improve on experimental tools to reach further stability. As tools are linked statically, it should be even possible to install tools using different versions of VG core next to each other; aside from incompatibilities in the launcher, which we would not allow. For experimental tools, IMHO a "exp-" is too cryptic. If you want to go this way, it should be "experimental-...". But instead, I just would abort with a good message when not run with an option "--yes-i-know-this-tool-is-experimental". Being interactive is bad when you want to run the tool from scripts. > Dirk, just to clarify -- you've asked lots of questions about the details, > which is good. But do you think it's a good idea in general? We have > approvals from Bart and Stephen, and an implicit approval from Robert. IMHO providing experimental tools is a good idea. Josef ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
