How do you describe systems in general with Haskell?
If you are to describe a system, which consists of several subsystems, how do you approach the problem? What types, classes, functions whatever do you introduce? I guess it is a common problem, is there a general method? Just to describe, not to solve (though if the description implies the solution then it is wonderful). Obviously this is not just a haskell-specific problem, but I think there might be people who are aware of the best current solution (category theory?). For a dummy example, how would you describe the system from a fox, goose and bag of beans puzzle (wolf, goat and cabbage)?
On 11-11-05 01:17 PM, Grigory Sarnitskiy wrote:
If you are to describe a system, which consists of several subsystems, how do you approach the problem? What types, classes, functions whatever do you introduce?
I guess it is a common problem, is there a general method? Just to describe, not to solve (though if the description implies the solution then it is wonderful).
I would try Michael Jackson's Problem Frames.
That look's interesting. Do you have experience using this method?
Arnaud
On Sat, Nov 5, 2011 at 7:09 PM, Albert Y. C. Lai
On 11-11-05 01:17 PM, Grigory Sarnitskiy wrote:
If you are to describe a system, which consists of several subsystems, how do you approach the problem? What types, classes, functions whatever do you introduce?
I guess it is a common problem, is there a general method? Just to describe, not to solve (though if the description implies the solution then it is wonderful).
I would try Michael Jackson's Problem Frames.
______________________________**_________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/**mailman/listinfo/haskell-cafehttp://www.haskell.org/mailman/listinfo/haskell-cafe
Well, I usually use whatever comes handy, but I'm sure there are other approaches — like, for example, trying something almost unusable first.
Отправлено с iPad
05.11.2011, в 21:17, Grigory Sarnitskiy
If you are to describe a system, which consists of several subsystems, how do you approach the problem? What types, classes, functions whatever do you introduce?
I guess it is a common problem, is there a general method? Just to describe, not to solve (though if the description implies the solution then it is wonderful).
Obviously this is not just a haskell-specific problem, but I think there might be people who are aware of the best current solution (category theory?).
For a dummy example, how would you describe the system from a fox, goose and bag of beans puzzle (wolf, goat and cabbage)?
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
Grigory Sarnitskiy
If you are to describe a system, which consists of several subsystems, how do you approach the problem? What types, classes, functions whatever do you introduce?
I guess it is a common problem, is there a general method? Just to describe, not to solve (though if the description implies the solution then it is wonderful).
Obviously this is not just a haskell-specific problem, but I think there might be people who are aware of the best current solution (category theory?).
In general I view the subsystems as completely separate, as far as possible. Then I write a library for each of them, combining them later in a program. Also I try to find a design pattern for the general problem at hand, although I almost always end up using FRP. Greets, Ertugrul -- nightmare = unsafePerformIO (getWrongWife >>= sex) http://ertes.de/
participants (5)
-
Albert Y. C. Lai -
Arnaud Bailly -
Ertugrul Soeylemez -
Grigory Sarnitskiy -
MigMit