[cfe-dev] [PATCH] MS compatibility flag implies delayed parsing

Aaron Ballman aaron at aaronballman.com
Sun Nov 6 15:39:59 PST 2011


On Sun, Nov 6, 2011 at 3:53 PM, Aaron Ballman <aaron at aaronballman.com> wrote:
> On Sun, Nov 6, 2011 at 2:53 PM, Eli Friedman <eli.friedman at gmail.com> wrote:
>> On Sun, Nov 6, 2011 at 12:12 PM, Aaron Ballman <aaron at aaronballman.com> wrote:
>>> There was a small discussion on IRC about the
>>> -fdelayed-template-parsing flag always going hand-in-hand with the
>>> -fms-compatibility flag.  Since the implication is already there (you
>>> don't really have ms compatibility without the delayed template
>>> parsing, to a certain extent), this patch makes it more explicit.  So
>>> when you pass the fms-compatibility flag, it automatically enables the
>>> fdelayed-template-parsing flag as well.  If the user really does want
>>> one without the other, they can always pass -fms-compatibility
>>> -fnodelayed-template-parsing.
>>
>> Concept is fine; the patch doesn't actually implement what you say it
>> does, though.  Specifically, -fms-compatibility
>> -fnodelayed-template-parsing won't work with this patch.

Here is a second attempt at the patch -- this time it works the way I
wanted it to work!  Thanks for the review.

~Aaron
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mscompat.diff
Type: application/octet-stream
Size: 3693 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20111106/ef3c3f07/attachment.obj>


More information about the cfe-dev mailing list