Skip to content
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

[#41] Fixed bug in macro_names rule #61

Merged
merged 3 commits into from
Jul 24, 2014

Conversation

jfacorro
Copy link
Contributor

No description provided.

@@ -3,6 +3,8 @@
-define (bad_name, "(no)").
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Invalid macro name bad_name on line 3. Use UPPER_CASE.

@@ -255,7 +255,7 @@ check_no_tabs(Line, Num, _Args) ->
-spec check_macro_names(binary(), integer(), [term()]) ->
no_result | {ok, elvis_result:item()}.
check_macro_names(Line, Num, _Args) ->
{ok, Regex} = re:compile("^ *[-]define *[(]([^,]+)"),
{ok, Regex} = re:compile("^ *[-]define *[(]([^,(]+)"),
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing space after "," on line 258

elbrujohalcon added a commit that referenced this pull request Jul 24, 2014
@elbrujohalcon elbrujohalcon merged commit ddc84e8 into master Jul 24, 2014
@@ -3,6 +3,8 @@
-define (bad_name, "(no)").
-define(GOOD_NAME, "(megusta)").
-define(wtf_NAME, "(yuno)").
-define(GOOD_NAME(Arg), "(megusta)").
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Invalid macro name GOOD_NAME(Arg) on line 6. Use UPPER_CASE.

@jfacorro jfacorro deleted the jfacorro.41.macro.names.rule.bug branch July 24, 2014 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants