Developer forums (C::B DEVELOPMENT STRICTLY!) > Compiler Framework Redesign
XML based compilers
Alpha:
For sorting these flags, I think there are several options:
* Internally maintain a list of which flags should only used during C compilation or only during C++ compilation. The user interface would look exactly the same, and all known flags (from the internal list) would be automatically sorted behind the scenes.
* Give compiler flags an additional option to categorize themselves as C/C++/both.
* Use one of the above options and add additional sections to the other compiler options and other linker options locations. This would allow the user to specify their own sorting of flags, however, it would alter the .cbp file-format.
* Alternatively, this same addition to the user interface could be created, but all sorting would be recorded in the type of list mentioned in the first option. This would not change the .cbp file-format, but the settings would only be saved into the user profile.
My personal preference is the first option. Which option do you (and anyone else who would like to voice their opinion) recommend I pursue? (Is there another choice I have not considered yet?)
killerbot:
option 1 is for sure a start. Might create some maintenance problems, but we could start that way.
oBFusCATed:
Or the best options (three) - separate the c and c++ compilers in different entries/compilers :)
MortenMacFly:
--- Quote from: Alpha on August 04, 2012, 09:54:56 pm ---By the way, am I correct in assuming the revert of this means that a visible note is preferred over a tool tip?
--- End quote ---
For such important things, yes. Most people don'T wait long enough that the tooltip shows. Also, there are platforms where there is no tooltip. So tooltip should really be a "tip", not to worry about if you don't know it.
MortenMacFly:
--- Quote from: oBFusCATed on August 05, 2012, 08:13:04 pm ---Or the best options (three) - separate the c and c++ compilers in different entries/compilers :)
--- End quote ---
Why would you do that? MSVC for example is one compiler for all. We shouldn't split up things like that. I think grouping visually is fair enough. And event hat I believe won't be used by most of the people. To be honest to me (and only me) it sounds a bit like an overkill. But maybe just because I fail to see the benefit for me (again: only for me).,
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version