On May 24, 1:16 pm, Matthew Wilson wrote:
> I'm working on a really simple workflow for my bug tracker. I want
> filed bugs to start in an UNSTARTED status. From there, they can go to
> STARTED.
>
I just wrote an article for the April issue of Python Magazine on how
to add embedded DSL code to
On 25 Mai, 01:46, Matthew Wilson wrote:
> On Sun 24 May 2009 03:42:01 PM EDT, Kay Schluehr wrote:
>
>
>
> > General answer: you can encode finite state machines as grammars.
> > States as non-terminals and transition labels as terminals:
>
> > UNSTARTED: 'start' STARTED
> > STARTED: 'ok' FINISHED
On Sun 24 May 2009 03:42:01 PM EDT, Kay Schluehr wrote:
>
> General answer: you can encode finite state machines as grammars.
> States as non-terminals and transition labels as terminals:
>
> UNSTARTED: 'start' STARTED
> STARTED: 'ok' FINISHED | 'cancel' ABANDONED
> ABANDONED: 'done'
> FINISHED: 'd
On 24 Mai, 20:16, Matthew Wilson wrote:
> I'm working on a really simple workflow for my bug tracker. I want
> filed bugs to start in an UNSTARTED status. From there, they can go to
> STARTED.
>
> From STARTED, bugs can go to FINISHED or ABANDONED.
>
> I know I can easily hard-code this stuff in
I'm working on a really simple workflow for my bug tracker. I want
filed bugs to start in an UNSTARTED status. From there, they can go to
STARTED.
From STARTED, bugs can go to FINISHED or ABANDONED.
I know I can easily hard-code this stuff into some if-clauses, but I
expect to need to add a
I'm working on a really simple workflow for my bug tracker. I want
filed bugs to start in an UNSTARTED status. From there, they can go to
STARTED.
>From STARTED, bugs can go to FINISHED or ABANDONED.
I know I can easily hard-code this stuff into some if-clauses, but I
expect to need to add a lo
