I too write mostly throwaway stuff. Obviously, terse languages are better suited for that than others.
Java makes me cringe. But my understanding is Java programmers use IDE's with autocomplete. They don't do much typing.
As for your pipe comment, are you a whiz with passing file descriptors? What do you think about chaining programs together in this way? Would that solve your pipe needs?
Maybe you could accomplish what you want using lex? The general paradigm is pattern-action, just like awk. Lots of flexibility in what you can create. You could create your own interpreter.
I like writing simple filters. I guess I have succombed to the UNIX voodoo. I think of everything as a stream of text.
I'd be interested to take a crack at your "capture group" problem, if you can give me an example of what it looks like.
There are many ways to do this (gawk sorta supports it, perl can do it easily enough with
perl -pe 'print "$1\n" if /the number is ([0-9]+)/'
but it's a bit cumbersome), but it would be much nicer if awk directly supported it.
Not sure what you mean about lex; if I decide to go ahead and write my ideal shell I could use it, but that's A Project, a large part of which is designing the syntax and deciding what commands to implement. And I'm lazy. :)
Can you give an example of some sample input and how you want the output to look? I'm stupid and this is the only way I can be sure I know what you're trying to do.
Java makes me cringe. But my understanding is Java programmers use IDE's with autocomplete. They don't do much typing.
As for your pipe comment, are you a whiz with passing file descriptors? What do you think about chaining programs together in this way? Would that solve your pipe needs?
Maybe you could accomplish what you want using lex? The general paradigm is pattern-action, just like awk. Lots of flexibility in what you can create. You could create your own interpreter.
I like writing simple filters. I guess I have succombed to the UNIX voodoo. I think of everything as a stream of text.
I'd be interested to take a crack at your "capture group" problem, if you can give me an example of what it looks like.