Re:Why Concatenative Programming Matters
by _delirium on Sunday February 12, 2012 @02:36PM
(#3582724)
That's one reason I've found the pipeline metaphor not great as a way of introducing concatenative languages. To me, the shell pipeline, which has a data-in/data-out streaming kind of flavor, generalizes (with multiple input/outputs) into dataflow languages, not into concatenative languages. There are definite connections between the paradigms, but imo the stack-manipulation is a different thing not present in stream/pipe based languages. The graphical music language Pd literally draws the pipelines as wires connecting input and output ports on functions (inspired by physical patch cables), which seems much closer to what I'd expect a generalized version of shell pipelines to look like.
[ Parent
| on HN ]
Re:Why Concatenative Programming Matters
by evincarofautumn on Sunday February 12, 2012 @02:51PM
(#3582767)
Statically typed concatenative languages are precisely dataflow languages. Dynamically typed ones aren’t, because they can have dynamic stack effects. But the diagrams in my article look just like PureData programs for a reason.
Re:Why Concatenative Programming Matters
by dkersten on Sunday February 12, 2012 @03:51PM
(#3582959)
Dataflow languages are what I'm most interested in these days when it comes to programming languages and I've always liked the symmetry between concatenative languages and pure dataflow languages (visual ones or just stream/flow based textual languages).
I've also been doing a lot of Max/MSP programming lately and really love working in its "passing messages along patch cables" system, but am frustrated by its lack of higher order objects and lack of aggregate data types (hell, it won't even let me create a list of lists).
What I really want is a Max/Pd-like language with richer set of data types (algebraic types with pattern matching would be a good start) which can be trivially and unambiguously converted between visual and textual representations. A concatenative language may make this a lot easier.
Re:Why Concatenative Programming Matters
by evincarofautumn on Sunday February 12, 2012 @04:30PM
(#3583101)
I think you’re really going to like Prog, then. It’s concatenative but focused on ADTs and pattern matching. Abstraction is easy thanks to quotation. I have some neat ideas in mind for an editor, as well, that would do just what you say—display a flow diagram of a program or selection as you edit. Concatenative languages are indeed, as the bland Wikipedia article puts it, “highly amenable to algebraic manipulation” of this sort.
Re:Why Concatenative Programming Matters
by jvoorhis on Monday February 13, 2012 @02:33AM
(#3584627)
I recommend you check out Faust, if you haven't already.
It's an applicative language created especially for audio DSP. It seems to bridge the gap you describe by providing dataflow combinators and a graphical representation for programs.