Literary Programming, Programming was the first, Literary was the second. The main purpose of the Code comment area markup method is to live Preview directly in the Code Editor Preview panel without exporting or any preprocessing. If you extend the Markdwon tag, you can implement the eval code, print result, display data visualization and other instruction tags, to achieve live programming, live test. In the code's comment area, You can use the markdown to draw flowcharts, tables, task lists, and display images on the live preview panel, enhance the readability of your code. Support any code editor that supports Markdwon Live preview, allowing the source code of any programming language to become rich text in real time. you only need a single line of regular replacement preprocessing, then you can use any Markdown parse or converter. comment area markup method can be applied to any programming language and any markup (including Org,rst, asciidoc, etc.), which is the greatest advantage. It don't break the syntax of any programming language, you can compile directly. Markdown Literary programming that don't break the syntax of any programming language (screenshot of comment without the HN formatting issues: ) It's always great to get a top-down perspective on the topology / architecture at the beginning of a complex program.Įxample copied from a program that fetches data from somewhere and prepares it and mounts it as a fuse file system: We sometimes use Monodraw for that in our team and it really made a difference. You don't realize how nice it is to have proper search functionality and the ability to open a file in multiple frames until you don't have it anymore. It beats the heck out of whatever 1990s-looking IDE they had me using to debug the project. I owe you a few beers.ĮDIT: That's also around the same time I started using VS Code, which was a huge help. Thank you to whoever made the decision to properly comment that code. There were whole PAGES of ASCII art, and it saved my butt. Timing diagrams, menu layouts, waveforms, LCD illustrations, etc. The comments were the only redeeming quality. Basically this was a very old and very crusty project. I don't think a single macro was used in the entire project. There were deliberately few functions in the program (almost everything was in the main loop), due to stack size limitations (it was a 23 byte stack I believe). Even worse, it was one big file (something like 17k lines).Īll of the main variables we're statically allocated for easier ram usage and eeprom saving. Normally that wouldn't matter, but this project was written in assembly. As is typical with these older products, the microcontroller that drove it was an 8051 (some SiLab part I think). It was an industrial spray controller for vinyards and such. I haven't created much ASCII art in my own code yet, but I've been VERY grateful to others who included it in a few of the legacy projects I've dealt with in the past.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |