Need DSL assistance

[swille]

I'm sort of pondering a project in which I think a DSL would be a good
fit for user programmability to control transactional flow. I'm
thinking about how the DSL might look, and have come up with something
like this:

get :approval, :from =3D> [:manager, :system_owner]
if :approval =3D=3D k
get :information, :request =3D> :clearance, :from =3D>
[erson_with_role, "Security Role"]
modify erson, :with =3D> [:clearance, :clearance_date =3D> :now]
notify :success =3D> [:requestee, :requestor]
else
notify :failure =3D> [:requestee, :requestor]
finish
end

# unrelated to the code above
push :change, f =3D> :cn, :to =3D> :accounts, :where =3D> ":attribute
=3D=3D ld_cn"


It would expand much deeper, but for now, that's what I have. Any
thoughts on how best to implement something like this, how I could
make it a little cleaner, and how I might deal with completing the
flow after a system failure would be much appreciated

 

[Kero]

I'm sort of pondering a project in which I think a DSL would be a good

fit for user programmability to control transactional flow. I'm
thinking about how the DSL might look, and have come up with something
like this:

Check slides about DSL from RubyConf and EuRuKo.

Also look at the ruby quiz #49 lisp game, where ppl jumped through some
hoops to get rid of colons and even commas.

+--- Kero ---------------------------------- kero@chello@nl ---+
| The last good thing written in C++ was the Pachelbel Canon |
| Jerry Olson |
+--- M38c ------------ http://members.chello.nl/k.vangelder ---+

 

[swille]

Check slides about DSL from RubyConf and EuRuKo.

Also look at the ruby quiz #49 lisp game, where ppl jumped through some
hoops to get rid of colons and even commas.

thanks for the pointers

 

[Wilson Bilkovich]

Sorry for the late reply here, but I'm still catching up on Ruby-Talk.
While I'm not actually advocating that you use this, because it's
probably more than you need.. anyone working on a DSL for business
processes should take a look at BPEL, at least to see what problems
they had to overcome.
http://en.wikipedia.org/wiki/BPEL
Even cooler would be a Ruby DSL that wrapped BPEL, because then your
DSL could inter-operate with non-Ruby code. Still, that's probably
more work than you're looking to do.

--Wilson.