-
-
Notifications
You must be signed in to change notification settings - Fork 610
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parser improvements to handle attributes #3696
Conversation
|
@WalterBright Could you merge this? I'd like to introduce "more strict" check for redundant/conflicting attributes in 2.066 release. This is the last piece for that. |
c99d24e to
ccaec7e
Compare
02a03f4 to
01503a9
Compare
7f0d387 to
b5c5844
Compare
|
@WalterBright ping. |
82543a9 to
f16c73f
Compare
|
@WalterBright This code logic cleanup has been proposed by you, in the PR #3689. @yebblies Do you have a time to review this PR? |
| { | ||
| OutBuffer buf; | ||
| StorageClassDeclaration::stcToCBuffer(&buf, stc); | ||
| if (*(buf.data + buf.offset - 1) == ' ') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason not to use indexing here instead of pointer arith? This whole construct is pretty nasty.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was no reason. I replaced it with pointer indexing.
Check redundant/conflicting attributes between prefix and postfix
… VarDeclaration I'd like to store all prefix attributes to `Declaration::storage_class`, but currently it's not possible because of these behaviors.
|
Okie dokie. |
|
Auto-merge toggled on |
Parser improvements to handle attributes
|
Thanks! |
I replace "storage class" word with "attribute" in diagnostic messages, because the latter is more general word.