Re: [Haskell-cafe] An idea to document inter department dependencies in Haskell

2012-03-14 Thread C K Kashyap
Thanks a lot Alberto, Actual code generation is not really my immediate goal ... What my immediate requirement is to validate the consistency of design changes. So essentially, this EDSL would not generate any target code - it's successful compilation would be the desired result and perhaps more

[Haskell-cafe] An idea to document inter department dependencies in Haskell

2012-03-13 Thread C K Kashyap
My dear Haskell folks, I work in a software company where I develop components that go into a really complex system that's built of several components developed by different teams that are geographically distributed. The components themselves run in a distributed manner across client and several

Re: [Haskell-cafe] An idea to document inter department dependencies in Haskell

2012-03-13 Thread Alberto G. Corona
Hi, Just thinking aloud : A way to start is to define concrete workflows for concrete events. What It is necessary to do if. This may make things more explicit and to clarify the problems. .Later, .maybe. these concrete workflows can be abstracted away from procedural/imperative to declarative