In my previous three posts, I explained why the semantics of programming languages are not as rich as they could be. I pointed out some symptoms of that deficit, and then made recommendations about bridging the gap. Finally I introduced “marks”–a feature of the
intent programming language I’m creating–and gave you a taste for how they work.
In this post, I’m going to offer more examples, so you see the breadth of their application.
Before I do, however, I can’t resist commenting a bit on the rationale for the name “marks”.
In linguistics, markedness is the idea that some values in a language’s conceptual or structural systems should be assumed, while others must be denoted explicitly through morphology, prosodics, structural adjustments, and so forth. Choices about markedness are inseparable from worldview and from imputed meaning. Two quick examples: