Hi Aaron, On Tue, Jul 1, 2014 at 9:40 PM, Aaron Ballman <[email protected]> wrote: > On Tue, Jul 1, 2014 at 3:15 PM, Alp Toker <[email protected]> wrote: > >> The input really is the MSC full version so -fmsc-full-version is the >> sensible name. Let's not invent new terminology like "extended version" >> here. > > There are zero options with "full" in their name. There are two-ish > options with "extended" in their name (fextended-identifiers and > fno-extended-identifiers), but they don't really qualify as examples > for this discussion. So both of these choices would qualify as > "inventing new terminology." > > The goal is to discuss what qualifies as a "sensible" name, and I have > some (relatively weak, but valid) objections to using "full" because > it implies you are required to specify the full version information > when that isn't the case.
I think Alp is refering to _MSC_FULL_VER from here: http://msdn.microsoft.com/en-us/library/b0084kay.aspx That said, I'm not sure this option is a perfect representation of that symbol. I don't like "extended version" either, so I'm going out on a limb: -fmsc-version-string? - Kim _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
