Re: Combining entry_call, accept_statment and terminate_statment

[Mark Lorenzen <mark.lorenzen@ofir.dk>]

"Randy Brukardt" <randy@rrsoftware.com> writes:

[cut]

>
> But I'd say that you probably have a design problem if you have a task that
> is both calling and accepting at the same time. That's pretty weird (unless
> the accepts are purely for task control, as above). It's preferable that
> each task be either a server (accepting entries) or a client (calling
> entries), but not both. Analysis is complicated if you have both.
>
>                       Randy.

To me, this seems to be a severe design limitation. Isn't it normal to
have a task acting as a filter, i.e. reading data from a PO,
manipulating the data and the writing the manipulated data to a PO?
This could f.x. be a task implementing a (de)multiplexer.

- Mark Lorenzen