10 ms·

> 2. Switch to object literal I've generally called a much more general form of this "data driven programming". (The data here being the mapping.) See: https:

> 2. Switch to object literal I've generally called a much more general form of this "data driven programming". (The data here being the mapping.) See: https://en.wikipedia.org/wiki/Data-driven_programming#Another_interpretation https://en.wikipedia.org/wiki/Data-driven_programming#Anothe... and the referenced https://homepage.cs.uri.edu/~thenry/resources/unix_art/ch09s01.html https://homepage.cs.uri.edu/~thenry/resources/unix_art/ch09s... > the important part is moving program logic away from hardwired control structures and into data

zwkrt 7y ago
Of course the logical conclusion of any data driven programming technique is to build a DSL and a parser. I always think that if my solution is starting to look like a compiler I’m doing something right since I’m modeling the domain and allowing end users to solve their own problems. After all, what is a compiler/interpreter of a Turing complete language if not (provably) the most flexible data-driven program?