4 ms·

Shouldn't it be like doE: doC, doB, doA doD: doB etc? anyways the problem with this approach is that doD() is assumed to be a general function (or statement

• flukus 8y ago
  > but rather in this specific case we need it to be executed after doB() is done. Why is that? If it needs any result from doB() then it is a dependencies that must be specified. If it needs to be done only after doB is successful then it is a dependency, just an implicit one we rely on the procedural execution to handle. In either case some sort of surrogate dependency (or better syntax) would have to be introduced. But the point is that either would necessitate or be aided by graphical programming.
  • lorean_victor 8y ago
    ok imagine doB() is a function that loads a record from the database and doD() is for example a password hash matcher (really imperfect example, just trying to get the point across). You might want to use both doB() and doD() in other contexts as well, so basically it is not the case that you would want to execute doD() always after executing doB(), neither is it the case that executing doD() always requires executing doB() beforehand. It just happens that in a specific case you would want to execute doB() and then pass its result to doD().