How to comment a grammar rule in yacc and a regex matching rule in lex?
up vote
0
down vote
favorite
I want to comment this matching rule in lex. I don't want to delete it. I just want it commented so anyone sees the lex file later be informed that this part has been commented
<tickPragma_name_1>. {
myyyless(0);
BEGIN (0);
}
how I can do that? I know that I can comment the C code inside the {} .but I want to comment the whole rule.
flex-lexer yacc lex
add a comment |
up vote
0
down vote
favorite
I want to comment this matching rule in lex. I don't want to delete it. I just want it commented so anyone sees the lex file later be informed that this part has been commented
<tickPragma_name_1>. {
myyyless(0);
BEGIN (0);
}
how I can do that? I know that I can comment the C code inside the {} .but I want to comment the whole rule.
flex-lexer yacc lex
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I want to comment this matching rule in lex. I don't want to delete it. I just want it commented so anyone sees the lex file later be informed that this part has been commented
<tickPragma_name_1>. {
myyyless(0);
BEGIN (0);
}
how I can do that? I know that I can comment the C code inside the {} .but I want to comment the whole rule.
flex-lexer yacc lex
I want to comment this matching rule in lex. I don't want to delete it. I just want it commented so anyone sees the lex file later be informed that this part has been commented
<tickPragma_name_1>. {
myyyless(0);
BEGIN (0);
}
how I can do that? I know that I can comment the C code inside the {} .but I want to comment the whole rule.
flex-lexer yacc lex
flex-lexer yacc lex
edited Nov 27 at 17:37
sepp2k
291k37592604
291k37592604
asked Nov 11 at 9:04
Amr Rady
42110
42110
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
You can surround the rule with /*
and */
, just as in C, but with two major caveats:
Everything needs to be indented by at least one space, including the
/*
(and, I believe, the contents).There cannot be any nested comments in the action.
Thanks, the indentation note made it works.
– Amr Rady
Nov 12 at 10:02
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
You can surround the rule with /*
and */
, just as in C, but with two major caveats:
Everything needs to be indented by at least one space, including the
/*
(and, I believe, the contents).There cannot be any nested comments in the action.
Thanks, the indentation note made it works.
– Amr Rady
Nov 12 at 10:02
add a comment |
up vote
2
down vote
accepted
You can surround the rule with /*
and */
, just as in C, but with two major caveats:
Everything needs to be indented by at least one space, including the
/*
(and, I believe, the contents).There cannot be any nested comments in the action.
Thanks, the indentation note made it works.
– Amr Rady
Nov 12 at 10:02
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
You can surround the rule with /*
and */
, just as in C, but with two major caveats:
Everything needs to be indented by at least one space, including the
/*
(and, I believe, the contents).There cannot be any nested comments in the action.
You can surround the rule with /*
and */
, just as in C, but with two major caveats:
Everything needs to be indented by at least one space, including the
/*
(and, I believe, the contents).There cannot be any nested comments in the action.
answered Nov 11 at 19:58
rici
150k19129194
150k19129194
Thanks, the indentation note made it works.
– Amr Rady
Nov 12 at 10:02
add a comment |
Thanks, the indentation note made it works.
– Amr Rady
Nov 12 at 10:02
Thanks, the indentation note made it works.
– Amr Rady
Nov 12 at 10:02
Thanks, the indentation note made it works.
– Amr Rady
Nov 12 at 10:02
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53247242%2fhow-to-comment-a-grammar-rule-in-yacc-and-a-regex-matching-rule-in-lex%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown