Re:Ferret: a Lisp implementation for real time embedded cont...
by antt on Tuesday July 31, 2018 @10:24AM
(#17653373)
There's singles of us!
If you want to extract it run M-x org-babel-tangle and you will end up with the usual source files and directories installed relative to the location of the org file.
I doubt there's a dozen people in the world that do it. But it is surprisingly useful and powerful when you get used to it. If anyone in Melbourne is interested in learning about this I have been toying with the idea of running a workshop on it.
I'm in the process of getting the detangle working for noweb mode. The current implementation fakes it with regex which force you to write code linearly instead of literately. But even if you can't detangle arbitrarily nested code it's magic to see changes in a source file appear in the right source code block.
Re:Ferret: a Lisp implementation for real time embedded cont...
by th0ma5 on Tuesday July 31, 2018 @12:27PM
(#17654547)
I know the rather spiffy project http://thi.ng uses org mode for literate programming and web site generation all from the source code. It doesn't seem to be all one big file, but I think each component may be a file.
Re:Ferret: a Lisp implementation for real time embedded cont...
by Touche on Tuesday July 31, 2018 @11:16AM
(#17653824)
How do you deal with having to scroll such a large file? That's the biggest turn-off to literate programming for me. I don't like code files more than a couple hundred lines of code. Search isn't enough for me.
Re:Ferret: a Lisp implementation for real time embedded cont...
by Jtsummers on Tuesday July 31, 2018 @12:10PM
(#17654416)
I mean, it isn't, if you organize your file identically to the source tree. But I break it out differently when I use this approach. I'll use the noweb references and scatter my code across the document in a logical way that's not reflective of the generated source tree.
For instance, I group all include or equivalent statements in an appendix, rather than within the primary code discussion. If a block of code can't be directly reused, but for some reason needs to be in every (or several) source files (think standard boilerplate), I'll write it once in a place that makes sense, and reference it from all the places where it actually gets tangled into the output.
Additionally, I include the Makefile (or whatever equivalent) and other scripts within this same document. Learning docker? Make a dockerfile in here, fully annotated, along with the shell commands to actually deploy it.
Mine will only mirror the original source tree if it's:
Very simple.
I've imported a bunch of code into it and don't, yet, know how to break it down.
An example C project may look like:
* Purpose Statement
* README
* Usage
This program can be executed from the command line by calling:
#+BEGIN_EXAMPLE
$ ./foo
#+END_EXAMPLE
It accepts the following command line parameters:
- =-c= :: something
- =-d= :: something else
** Implementation
To process the command line flags we use <some library>.
it has the following API calls...
Here's the code for processing our commands...
* Business Logic
We communicate with the server via some REST API described in <location>
and <library> to make the calls.
-- Here I'd intermingle the REST API I'm using and the C API I'm producing
-- for my own consumption, or something similar.
* Code that's not fully organized yet
** Main Function
This is the entry point, blah, blah, blah:
#+BEGIN_SRC c :noweb yes :tangle src/main.c
#+END_SRC
* Appendix: Includes
Re:Ferret: a Lisp implementation for real time embedded cont...
by emidln on Tuesday July 31, 2018 @04:09PM
(#17656634)
When your IDE (or Emacs in this case) offers go jumping/searching functionality, it doesn't really matter how many files your code is in. When I used bare vim, I cared a lot more about code organization than I do with an IDE that makes jumping around the codebase easy.
Re:Ferret: a Lisp implementation for real time embedded cont...
by omaranto on Tuesday July 31, 2018 @01:48PM
(#17655309)
That's called literate programming. Maybe the most famous example is the source code for TeX, a single ~25,000 line file (http://tug.org/texlive/devsrc/Build/source/texk/web2c/tex.we...) that can be used to make a TeX compiler, or produce a book explaining the implementation.
Re:Ferret: a Lisp implementation for real time embedded cont...
by eigenspace on Tuesday July 31, 2018 @10:29AM
(#17653412)
I actually just started dong this a few days ago and I’m loving it so far. I have it configured so that every time I save, emacs runs org-tangle and all my code ends up in the proper directories but I never have to touch it there, I can just stay in org mode and keep different ‘files’ of code in different collapsible sections making moving around much easier!
Re:Ferret: a Lisp implementation for real time embedded cont...
by antt on Tuesday July 31, 2018 @10:35AM
(#17653473)
Look at org-babel-detangle and have your mind blown[0].
[0] Mostly, the current implementation works only with source blocks that are linearly added one after the other and don't use the <<noweb reference>> in code blocks.
Re:Ferret: a Lisp implementation for real time embedded cont...
by antt on Tuesday July 31, 2018 @10:31AM
(#17653433)
This has been my go-to way of programming anything where I'm the primary person responsible for it.
With pandoc you get a system that can export to any format under the sun. The highlight so far was exporting a problematic code portion with the literate explanation around it and a pretty basic asymptotic analysis in latex to docx, code highlighting, math formulas, tables all worked without human intervention. It ended up in a power point that I'm told was very well received.
Re:Ferret: a Lisp implementation for real time embedded cont...
by enitihas on Tuesday July 31, 2018 @12:20PM
(#17654492)
Just curious, how does github manages to render org files so flawlessly, including embedded code snippets. I thought emacs was the only popular environment supporting org files.
Re:Ferret: a Lisp implementation for real time embedded cont...
by eigenspace on Tuesday July 31, 2018 @02:18PM
(#17655623)
Github seems to play quite well with Org. Little known fact: If you give your repo a README.org instead of a README.md, github will show that file just like how it shows a regular README.md.
Re:Ferret: a Lisp implementation for real time embedded cont...
by peatmoss on Wednesday August 01, 2018 @09:25AM
(#17662244)
Unfortunately, the same can't be said of Bitbucket. At one point I voted for or commented on a feature request for it, and I pretty routinely get notified when someone else discovers the lack of org-mode support on Bitbucket.
At this point, I'm convinced Atlassian hates happiness, or there is some shameful architectural reason why they cannot support more than Markdown for their READMEs. Given the number of vociferous responses to that feature request, there would appear to demand.
Re:Ferret: a Lisp implementation for real time embedded cont...
by nanomonkey on Tuesday July 31, 2018 @01:16PM
(#17655018)
The first time I came across this it was touted as Clojure that compiled down to C++11. Now I'm seeing it listed as a generic lisp. I'm curious if that's due to the limitations of writing for embedded systems (using d-list instead of hash tables, memory management, etc.) or are there other deviations?
Re:Ferret: a Lisp implementation for real time embedded cont...
by nakkaya on Thursday August 02, 2018 @06:29AM
(#17670422)
You are right. It is due to limitation of writing for embedded systems. I try to keep everything as close to Clojure as possible but some stuff is just not possible on embedded systems or behave a little bit different.
Re:Ferret: a Lisp implementation for real time embedded cont...
by nakkaya on Thursday August 02, 2018 @06:53AM
(#17670526)
If I were to go with C I would have to reimplement OOP machinery required for an object system. OOP also makes memory management a non issue. Functions are first class citizens in Lisp so functors/lambdas makes it real easy to create closures. std::atomic combined with Clojure semantics makes sure there no race conditions. std::thread / std::future makes multi threaded programming much easier. Templates help with picking and choosing which components to include (i.e there are multiple memory managers to pick from.). etc. etc. Non of the above is essential and can be done in C but why bother, GCC/LLVM people are much better at this then I can be including platform specific tricks for different architectures. Modern C++ is very close to Lisp after all it only takes 6 passes over the Clojure code to generate C++ code. (Compiler makes more than 6 passes but others are for optimization.)
If you want to extract it run M-x org-babel-tangle and you will end up with the usual source files and directories installed relative to the location of the org file.
I doubt there's a dozen people in the world that do it. But it is surprisingly useful and powerful when you get used to it. If anyone in Melbourne is interested in learning about this I have been toying with the idea of running a workshop on it.
I'm in the process of getting the detangle working for noweb mode. The current implementation fakes it with regex which force you to write code linearly instead of literately. But even if you can't detangle arbitrarily nested code it's magic to see changes in a source file appear in the right source code block.
I'm on the opposite side of the planet but I'd be interested, if you did an article or video on whatever you would teach in the workshop.
Though I have met a few people who use org mode as an organizer/planner.
Just don’t tell me “you can see the context” as any proper codebase would probably not be linear in code flow anyway.
For instance, I group all include or equivalent statements in an appendix, rather than within the primary code discussion. If a block of code can't be directly reused, but for some reason needs to be in every (or several) source files (think standard boilerplate), I'll write it once in a place that makes sense, and reference it from all the places where it actually gets tangled into the output.
Additionally, I include the Makefile (or whatever equivalent) and other scripts within this same document. Learning docker? Make a dockerfile in here, fully annotated, along with the shell commands to actually deploy it.
Mine will only mirror the original source tree if it's:
Very simple.
I've imported a bunch of code into it and don't, yet, know how to break it down.
An example C project may look like:
Some people use several Emacs windows (or frames or whatever) but all of them peeking into the same file, but in to different locations of it.
[0] Mostly, the current implementation works only with source blocks that are linearly added one after the other and don't use the <<noweb reference>> in code blocks.
With pandoc you get a system that can export to any format under the sun. The highlight so far was exporting a problematic code portion with the literate explanation around it and a pretty basic asymptotic analysis in latex to docx, code highlighting, math formulas, tables all worked without human intervention. It ended up in a power point that I'm told was very well received.
At this point, I'm convinced Atlassian hates happiness, or there is some shameful architectural reason why they cannot support more than Markdown for their READMEs. Given the number of vociferous responses to that feature request, there would appear to demand.
Pandoc has a pretty decent Org Mode parser and writer.
Update: It needs to be extracted from an org file, and by default Github renders the org file so that the source is not visible.
https://raw.githubusercontent.com/nakkaya/ferret/master/ferr...
What feature of C++ does this need that is so compelling as to cut it off from use on straight C?