Sep-05-2019, 02:25 PM
@Alfalfa okay I have never in my years experienced a situation in a single application where what you describe would exist and if it did exist I would say it was a poor design to begin with. You should never have a need in a single thread application to broadcast a command since everything is for the most part linear -- as in you can only process one path at a time -- creating something like you describe would mostly likely end up being a debugging nightmare (I have had to work on stuff where someone did something that hopped all over the place based on events and it had a bug -- it took a while to track it down and then they asked me to re-code it so that it was not such a nightmare later on -- and frankly the re-write was I think 3x to 5x faster and definitely easier to follow and maintain)
Further yes I am to against spaghetti calls and/or spaghetti code for that matter. I believe in the K.I.S.S. principle (Keep It Simple and Smart) which means do not use something more complex than what your code calls for. Yes sometimes complex methodologies are needed but using one when it is not needed is just not Smart and can lead to unnecessary issues later on.
Further yes I am to against spaghetti calls and/or spaghetti code for that matter. I believe in the K.I.S.S. principle (Keep It Simple and Smart) which means do not use something more complex than what your code calls for. Yes sometimes complex methodologies are needed but using one when it is not needed is just not Smart and can lead to unnecessary issues later on.