Workflows are usefull if you are doing the same thing over and over again (for example in the maybe-"workflow" your do something, get a value and go on in the workflow or get nothing and stop the workflow returning nothing).

Just take a look at the "bind" - you are chaining monads - that means values with additional informations, and this "additional info structure" stays the same, only the value might change (it's rather hard to explain i guess ;) )

Looking at your problem - there is no common structure - only a major strategie to solve common problems. It might be a workflow in the common sense but not in F# (maybe "workflow" was not the best name after all).

By on 4/15/2009 9:28 PM ()

Yes, that's a good answer - I mean the bit about "workflow syntax is useful if you're doing the same thing over and over again".

So this isn't a good candidate for a computation expression in the F# sense (computation expression is the name we use in the spec). Instead it looks like you should just use regular functional programming to solve your problem here.

Kind regards

don

By on 4/16/2009 7:57 AM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper