your the only person that made this make sense for me. It clicked in a different way though. It makes sense in code where you type an IF => THEN statement.The code will only execute when P is fulfilled; the output will be whatever Q is. On the other hand if P is never fulfilled then Q is never outputted. I guess im thinking of it as a type of "LAW" statement. it can only ever be tested when the P conditions are met; if they're not then the code sits their in the background. Maybe my thinking is flawed lol. sometimes an idea clicks and then I apply it somewhere else and my "reasoning" ends up false. Thank you for the lesson though this has been extremely helpful!!!
your the only person that made this make sense for me. It clicked in a different way though. It makes sense in code where you type an IF => THEN statement.The code will only execute when P is fulfilled; the output will be whatever Q is. On the other hand if P is never fulfilled then Q is never outputted. I guess im thinking of it as a type of "LAW" statement. it can only ever be tested when the P conditions are met; if they're not then the code sits their in the background. Maybe my thinking is flawed lol. sometimes an idea clicks and then I apply it somewhere else and my "reasoning" ends up false. Thank you for the lesson though this has been extremely helpful!!!
Your example makes me sense and I understood it better. Thanks a million! :)