| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Support VHDL alias constructs.
* Translate class to "Design Unit" for VHDL.
* Fix compile error
* Add new function trDesignUnitDocumentation() to translator.
Adapt english and german translation to use the new function.
Co-authored-by: Andreas Regel <andreas.regel@newayselectronics.com>
|
|
|
|
| |
because it is generated from vhdlparser/CMakeLists.txt
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* issue #7778 Build fails with javacc 5.0
At the moment doxygen works with javaCC version 7.0.5 but no test is done for the version. The minimum requirement has been set to 7.0.5
javacc does not have an option to retrieve the version though when giving `--version` a bit more information is given, this information is filtered.
(an issue has been submitted to javacc to obtain the version information: https://github.com/javacc/javacc/issues/172).
* issue #7778 Build fails with javacc 5.0
Version detection did not work for `5.0` (only x.y.z was handled, not x.y)
* issue #7778 Build fails with javacc 5.0
Based on a review
- `--version` is not a valid option, but present already for future use but
- removed double ` if(JAVACC_EXECUTABLE)`
- Needed `"${JAVACC_TEMP_VERSION}"` as otherwise when `javacc` is found but cannot be executed a message like:
```
CMake Error at cmake/FindJavacc.cmake:11 (string):
string sub-command REGEX, mode MATCH needs at least 5 arguments total to
command.
Call Stack (most recent call first):
vhdlparser/CMakeLists.txt:1 (find_package)
```
would appear
- reformulated some status strings
* issue #7778 Build fails with javacc 5.0
the `.` was not correctly escaped.
* issue #7778 Build fails with javacc 5.0
Another one 7.0........ match, going for the suggested match in the cmake CheckCXXCompilerFlag
* issue #7778 Build fails with javacc 5.0
Accidently left debug statement.
* issue #7778 Build fails with javacc 5.0
Problem has been fixed upstream for version 7.0.7 and up, not using `--version` but `-version` as all command line arguments are starting with a single '-'.
Also it is just the bare version, so small extra test so it will work with all versions.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When having a vhdl construct like:
```
entity _H_ is
```
we get the, a bit unclear, warnings like:
```
Lexical error at: 16:8. Encountered: _ after: .
```
with version 1.8.17 we got the warning:
```
.../vhdl.vhd:16: warning: Lexical error, Encountered: '_' after: ''
```
not 100% clear either but at least clear which file is involved and what the meaning of the '16' is.
Also the message didn't conform the doxygen style / place / handling of warnings / errors anymore (didn't go to the WARN_LOGFILE anymore).
(The message is correct as a vhdl identifier cannot start or end with an underscore.
Between the used javaCC versions (now 7.05) and the previously used version 6.xx apparently a small in the error handler prototypes has been introduces, and thus not finding the doxygen version anymore.
|
| |
|
|
|
|
| |
void and virtual void functions
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |\ |
|
| | |\
| | | |
| | | | |
Adding JAVACC_FLAGS for javacc compilation
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
During transition to cmake build the, essential for debugging, flag possibility was not added.
(Added analogous to LEX_FLAGS and YACC_Flags).
Available debug options (according to old Makefile):
`-debug_parser`
`-debug_token_manager`
`-debug_lookahead`
|
| | | | |
|
| |\ \ \
| | |/ /
| |/| |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_7436
|
| | |/
| | |
| | |
| | |
| | |
| | | |
The search for `/*` or /*!` ended at the last `*/` in a file and thus skipping other intermediate block end and new starts. Also the intermediate code was lost see as comment.
The filter pattern used was incorrect and should have been `<"/*" (~["*"])* "*" ("*" | ~["*","/"] (~["*"])* "*")* "/">` (thanks to https://javacc.org/contrib/C.jj).
Here also the space plus one or more `*` at the end beginning of the line are still incorporated as well as multiple `*` before the colosing `*/` this is also filtered.
|
| | | |
|
| |/ |
|
| |\
| | |
| | | |
issue #7313 VHDL attribute 'subtype is not supported and breaks parser
|
| | |
| | |
| | |
| | | |
Add the `'subtype` construct for variables etc.
|
| | |
| | |
| | |
| | | |
free issues
|
| | | |
|
| | | |
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Spelling corrections as found by codespell and in #561.
`assume_guarentee` is not a vhdl keyword, `assume_guarantee` is.
A number of spelling errors are in generated code (through javacc) and have been reported upstrean (https://github.com/javacc/javacc/pull/118)
Corection of `guarded_signal_specificatio` to `guarded_signal_specification` is not possible as `guarded_signal_specification` exists as well.
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
| |
- possibility to find the javacc program / script
- creating command to compile javaparser.jj with javacc and place files in the right directory when javacc is present.
|
|
|
|
|
|
| |
The generated vhdl code files (.cc and .h) and didn't match the vhdl input source (vhdlpardser.jj).
When regenerating with javacc the vhdl code file they didn't compile.
vhdlparser.jj has been corrected.
|
| |
|
|
|
|
|
|
| |
Generate configvalues.h only as a dependency for the VHDL parser. Fixes
a problem in combination with Ninja v1.9.0 because of duplicate rules
for generating configvalues.h.
|
| |
|
| |
|
|\
| |
| | |
Making VHDL error messages more doxygen like
|
| | |
|
| |
| |
| |
| | |
Found via `codespell`
|
|/
|
|
|
|
|
|
| |
JavaCC contains by default options to get more information about the parser paths used (analogous to the -d option of flex).
- Makefile
- adding option (JAVACC_FLAGS) for easier use of JavaCC options
- adding possibility to reset generated files to their git versions.
- vhdlstring.h adding functions required by debug options (debug_token_manager)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Marking the resulting JS in this way ensures that visitors to the
resulting HTML documentation do not have to choose between running
non-free JS and experiencing the HTML documentation as it was
intended.
The JS was already freely licensed, so this change just
ensures that the appropriate labelling occurs so that GNU LibreJS [0]
parses the JS correctly as freely licensed.
[0] https://www.gnu.org/software/librejs/
Signed-off-by: zachwick <zach@zachwick.com>
|