But no, there's always one. :-)
I agree. This idea doesn't receive enough attention. If you pick your constraints you can make a particular envelope of uses easy and ones you don't care about hard.
AWK's choice to be a per line processor, with optional sections for processing before all lines and after all lines is self-limiting but it defines a useful envelope of use.
Not sure what that would mean. I think the tool was designed to be a user's programming language. I liken to think that `awk` was the Excel + VBScript of its days.
Now, you've posted a compiler/interpreter in awk for a C-like language that could allow easier porting of a C compiler's source. Hmmm. The license would have to be BSD so the BSD's could use it, too. Or pieces of it in my own solution.
I have a feeling whatever comes out of this won't make it into next edition of Beautiful Code. ;)
Let me also say that if you actually want to use this for anything you're crazy. I wrote it when I was... younger... and when I had no idea what I was doing. The only thing it's useful for these days is looking at and laughing at.
AFAIK they're both ubiquitous, though you might need a particular awk like gawk for library functions, depending on what you need to do. Nowadays I'm way more likely to use Python, though of course it's a much bigger dependency.
Sorry about the injury, and good luck -- I'd like to hear how it goes.
Thanks for sharing awklisp. Nice reading for a Sunday morning.
Here is the result: https://github.com/dbohdan/all-caps-basic. It targets C and uses libgc along with antirez's sds for strings. The multi-pass design with each pass consuming and producing text is intended to make the intermediate results easy to inspect, making the compiler a kind of working model. The passes are also meant to be replaceable, so you could theoretically replace the C dependencies with something else or generate native code directly in Awk. You can see some code examples in test/. Unfortunately, the compiler is very incomplete. I mean to come back to it at least to publish an implementation of arrays.
Which meant that it was perfectly allowable for it to be hacky and non-future proof, which it was.
Here's part of the code which read local variables definitions (in C-like syntax):
function do_local( \
nt, st, n, t){
nt = readtype()
st = tokens
ensuretoken(readtoken(), token_word)
n = tokens
outofscope(n, 1)
ldb[n] = "var"
ldb[n, "type"] = st
ldb[n, "sp"] = sp - spmark
emit("# local " n " of type " st " at " (sp-spmark) "\n")
tokens is the value of the current token, ldb is the symbol table; you can see how I'm faking a structure using an associative array indexed by keyword.There's nothing actually very wrong with this code, but there's no type safety, barely any checking for undefined variables, no checking for mistyped structure field names, no proper data types at all, in fact... awk wouldn't scale for making the compiler much more complicated than it currently is. But it did hit the ideal sweet spot for getting something working relatively quickly for a one-shot job. It's still really good at that.
* Cannot have an array as an input to a function
* Cannot return an array from a function
* Meta-programming or pointers are only (barely) available in gawk
* There is an `@include` statement for `gawk` that is not part of POSIX, and there is no name spacing involved.
* Functions names can only exist in the global name space
There are some reasons somebody felt an urge to create perl... Still loving awk, and using it every day for text processing jobs.
Larry Wall (creator of Perl) says something pretty close to that here[1]:
"I was too lazy to do it in awk because it would have been hard to get awk to jump through the hoops I was wanting it to jump through. I was too impatient to wait for awk to finish because it was so slow. And finally, I had the hubris to think I could do better."
http://cahighways.org/wordpress/?p=8019
http://ieeexplore.ieee.org/document/213253/
BLACKER's heavy lifting in security was done by high-assurance kernel called GEMSOS:
http://www.cse.psu.edu/~trj1/cse443-s12/docs/ch6.pdf
It was a classified work for TRW whose details took a long time to get released. Might be why he rarely mentioned the BLACKER project in its origins. Possibly trying to obfuscate it a bit to avoid breaking laws.
This is neat! Question for you regarding the formatting/syntax used-
Why the slash-newlines in function declarations?
E.g.
function scope(name, \
s) {
To bytecode; I wanted to use the awk-based compiler as the initial bootstrap stage for a self-hosted compiler. Disturbingly, it worked fine. Disappointingly, it was actually faster than the self-hosted version. But it's so not the right language to write compilers in. Not having actual datastructures was a problem. But it was a surprisingly clean 1.5kloc or so. awk's still my go-to language for tiny, one-shot programming and text processing tasks.
http://cowlark.com/mercat (near the bottom)
(...oh god, I wrote that in 1997?)