Bug 5429 – Create product/component for D language/frontend

I have a few bugs/ER to log which concern the D language itself, and are not probably not worth writing a DIP by themselves. (if they are, this will be discussed in the issue.) It is not clear under which component they should be logged. After digging a lot I found that it probably should be: D/websites: "Problems with the contents of www.digitalmars.com and other sites managed by walter, including the language specification" (sic) I think that under D product, there should be at least 2 other components: language -> D Language itself (implementation independant; e.g. grammar) frontend -> Front-end, used by DMD, GDC, LDC, ... But another possibility is to extend the product list to have it more consistent: Product Components Language ... Frontend ... DMD GDC dstress Runtime Phobos Tools coffimplib,htod,installer,make,optlink Website This would make things clearer and more organized. For example: Allowing bang in template declaration: Can write: template Tpl( TemplateParameterList ) {...} void FuncTpl( TemplateParameterList ) {...} Should be able to write: template Tpl!TemplateParameter {...} void FuncTpl!TemplateParameter {...} template Tpl!( TemplateParameterList ) {...} void FuncTpl!( TemplateParameterList ) {...} Or: Allow while( auto a = <Expression> ) {...}

Indeed, when you look at the bugs under D/websites, there are very unrelated things: - Broken links in the website(s) - Documentation related bugs - Language related things - ABI stuff - Various runtime errors... So the other products/components should be make more explicit: Language/ABI Documentation by itself should be orthogonal to all products/components, as it is done for versions. I will continue commenting on this bug until things are completely clear, then maybe propose a complete new structure. We should then discuss on the way to reorganize that, if you are ok. I may then dump the base, create a migration script, apply it, either put the new db available somewhere for testing, and if good, give you the script so you can apply it on the master db. Notes: Language product should have components Grammar & ABI Orthogonal Documentation: Doc Only -> Only a documentation bug Need update -> Also need a doc update Doc OK -> Nothing to change in doc

Please start discussions about changes in the newsgroups. Only after there's some sort of consensus would any of these sorts of changes be made.