|
Bugzilla – Full Text Bug Listing |
| Summary: | bison: clarify parameter declaration | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Michal Suchanek <msuchanek> |
| Component: | Development | Assignee: | Michael Matz <matz> |
| Status: | NEW --- | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | proposed patch | ||
upstream? Have not done the paperwork for talking to GNU upstream. Doesn't this already follow from the use of singular form in
Directive: %parse-param {ARGUMENT-DECLARATION} ...
and the example that uses two arguments with separate braces:
%parse-param {int *nastiness} {int *randomness}
? I guess being more explicit doesn't hurt, though.
It's kind of 'if you know how it is you can see it there' thing. As in if you have no idea how it's implemented internally it's not clear at all. The other option would be bison refusing multiple arguments in one %parse-param but it does not. Documenting the deficiency sounds easier than fixing it. |
Created attachment 871602 [details] proposed patch Patch clarifying parameter declarations.