They are computationally equivalent. Except that you can't typecheck actor calculus (since you can send anything to an actor) but you CAN typecheck pi calculus (channels).
It's not entirely that bad in CL: (locally (declare (optimize (safety 3))) (defun list-int-p (list) (every #'integerp list)) (deftype list-int () `(satisfies list-int-p)) (defun xxx (list) (declare (type list-int list))…
For modelling to work generally (in most/all domains), you need some underlying paradigm all these models can be translated into. For excel, it's grid based dataflow, (for example, you can call it differently). I saw…
They are computationally equivalent. Except that you can't typecheck actor calculus (since you can send anything to an actor) but you CAN typecheck pi calculus (channels).
It's not entirely that bad in CL: (locally (declare (optimize (safety 3))) (defun list-int-p (list) (every #'integerp list)) (deftype list-int () `(satisfies list-int-p)) (defun xxx (list) (declare (type list-int list))…
For modelling to work generally (in most/all domains), you need some underlying paradigm all these models can be translated into. For excel, it's grid based dataflow, (for example, you can call it differently). I saw…