{"id":100,"date":"2022-01-29T15:03:26","date_gmt":"2022-01-29T06:03:26","guid":{"rendered":"http:\/\/blogs.harvard.edu\/adamnoto\/?p=100"},"modified":"2022-01-30T23:26:15","modified_gmt":"2022-01-30T14:26:15","slug":"the-best-ide-for-working-with-lex-and-yacc-bison","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/adamnoto\/2022\/01\/29\/the-best-ide-for-working-with-lex-and-yacc-bison\/","title":{"rendered":"(The Best) IDE for working with Lex and Yacc\/Bison"},"content":{"rendered":"

It’s painful to code something without an adequate IDE isn’t it? If you have been searching for the best IDE for Yacc\/Lex, I think we faced the same challenges. But just to save your time: for Linux\/macOS users: try Vim. I personally use CLion and Xcode, though.<\/p>\n

<\/p>\n

It seems like there’s no IDE offering proper syntax highlighting, indentation, and code intellisense for editing\u00a0both<\/em> Lex and Yacc. It might be because not many people edit Yacc and Lex day-to-day as part of their work. I myself won’t be coding them if it’s not for the compiler class<\/a> I am taking this semester.<\/p>\n

Or, maybe, it’s just difficult if not bordering impossible to come up with the perfect grammar\u00a0thingy<\/em>\u00a0(like, tmLanguage JSON file<\/a>) so that color highlighter, indentation and so on would just work\u2122, considering that Lex and Yacc each use a host language such as C in addition to their own constructs, effectively making them to be just as difficult as HTML<\/a> to be parsed with regular<\/em> expressions.<\/p>\n

Anyway, anything is better than Notepad certainly, no!?<\/p>\n

I have tried Vim, NeoVIM, Textmate, Emacs\/Spacemacs, Visual Studio Code, Sublime, XCode, the<\/em>\u00a0Visual Studio, Atom, and CLion. I’d say: Vim is probably the best overall, albeit there are some irritating issues in Vim. So<\/em>, be prepared \ud83d\ude42<\/p>\n

\"Editing

Editing Yacc and Lex in Vim<\/p><\/div>\n

Especially when editing Yacc files. Vim is inconvenient as the indentation just didn’t work. For example, when I type\u00a0if<\/code>\u00a0something something, and then pressed enter, I thought the cursor would be indented but it didn’t. Strangely tho<\/em>, Lex did not exhibit this problem at all. It was smooth sailing with Lex files.<\/p>\n

For other IDEs, you may skip CLion and the macOS version of Visual Studio as they do not recognize Lex and Yacc files at all. Maybe, Visual Studio will behave differently on Windows<\/a>, but I couldn’t verify. The\u00a0macOS version of Visual Studio does not support C\/C++<\/a>\u00a0; only C# and mobile.<\/p>\n

\"Editing

Editing a Lex file like a Text file on macOS Visual Studio<\/p><\/div>\n

A JetBrains user<\/a>\u00a09 years ago has asked for the much-needed Lex and Yacc support. But… their representative couldn’t do much as “there is pretty small interest in the topic.”<\/p>\n

It’s rather surprising. No doubt. Many would expect CLion and other paid JetBrains IDEs to have some kind of support, at least syntax highlighting and proper indentation if nothing else, since those products are aimed for professionals. I hope someday they’ll support Yacc and Lex.<\/p>\n

Anyway. Yeah, we can simply cross them out for now. But I still use CLion nevertheless, please continue reading.<\/p>\n

\"Inconsistent

Inconsistent syntax highlighting on Emacs<\/p><\/div>\n

Now, between VSCode, Sublime, Textmate, Emacs\/Spacemacs and Atom, I really can’t choose. All of them offered only nominal support. They all have serious issues with syntax highlighting, issues which Vim has none. Sad.<\/p>\n

Onto XCode… surprisingly, it checked the decent syntax highlighting requirement. And, this one not surprisingly<\/del>, it has the most pleasing user interface to edit those Lex\/Yacc files with. Although, I find the fact that I can’t have access to the terminal from within the IDE a rather painful experience.<\/p>\n

\"Editing

Editing a Lex file in XCode<\/p><\/div>\n

But, I still admire this IDE’s look and feel.<\/p>\n

\"Editing

Editing Yacc on XCode<\/p><\/div>\n

Pretty UI asides, the experience of editing Yacc files in XCode warrant some betterment.\u00a0For example, let’s consider we have the following rules:<\/p>\n

\r\nscreens: \/* empty *\/\r\n       | screens screen\r\n       ;\r\n<\/pre>\n
If I wanted to add an action next to the screen<\/code>\u00a0non-terminal on the second line, Xcode will indent the whole line incorrectly upon seeing the opening brace ({<\/code>) …to be:<\/p>\n
\r\nscreens: \/* empty *\/\r\n| screens screen {\r\n       ;\r\n<\/pre>\n
Not only that,\u00a0the syntax highlighter for C (within Yacc files) is buggy. I noticed how some function calls were highlighted with blue while others did not. It happened occasionally, and when I overwrite the function with the same name, it’s highlighted correctly.\u00a0I also could not replicate this kind of issue after restarting the IDE.<\/p>\n
So yeah, Vim is generally the most sensible choice overall. If it’s the only choice available.<\/p>\n
But indeed, there’s no single\u00a0best IDE.<\/p>\n
Xcode exhibited issues with rules\/productions indentation, as does Vim with the subroutines part. Personally, I simply turned off XCode’s automatic indentation to help<\/em> it stop from being that much annoying. In that way, XCode has supplanted Vim for me.<\/p>\n
I’d then use CLion to edit C files as it has the best-in-class intellisense for my C files.<\/p>\n
If I were a Windows user, however, I’ll not miss giving Visual Studio a try. It seems Visual Studio on Windows has excellent support for C\/C++ in addition to Lex and Yacc.<\/p>\n
In any case, they are all better than Notepad.<\/p>\n
Good luck.<\/p>\n","protected":false},"excerpt":{"rendered":"
It’s painful to code something without an adequate IDE isn’t it? If you have been searching for the best IDE for Yacc\/Lex, I think we faced the same challenges. But just to save your time: for Linux\/macOS users: try Vim. I personally use CLion and Xcode, though.<\/p>\n","protected":false},"author":10207,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6317],"tags":[],"class_list":["post-100","post","type-post","status-publish","format-standard","hentry","category-engineering"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/adamnoto\/wp-json\/wp\/v2\/posts\/100","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/adamnoto\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/adamnoto\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/adamnoto\/wp-json\/wp\/v2\/users\/10207"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/adamnoto\/wp-json\/wp\/v2\/comments?post=100"}],"version-history":[{"count":29,"href":"https:\/\/archive.blogs.harvard.edu\/adamnoto\/wp-json\/wp\/v2\/posts\/100\/revisions"}],"predecessor-version":[{"id":157,"href":"https:\/\/archive.blogs.harvard.edu\/adamnoto\/wp-json\/wp\/v2\/posts\/100\/revisions\/157"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/adamnoto\/wp-json\/wp\/v2\/media?parent=100"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/adamnoto\/wp-json\/wp\/v2\/categories?post=100"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/adamnoto\/wp-json\/wp\/v2\/tags?post=100"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}