> Yes. And it doesn't describe statemachines. Were he to change > `then determines the next thing that you do' into `then > determines the next thing that you do and waits for some > other kind of input' it would effectively describe > statemachines.
No it doesn't! A State machine reads input and changes state depending on that input That's all it does. It certainly doesn't read an input decide what state to go to and then wait for more input before changing state which is what your definition immplies! > Besides, I find it interesting that discrete mathematics, and > in particular counting problems, have barely been mentioned > in this thread. One of the few things I find myself doing > extremely often is estimate how much work my program will > need to do to solve a particular problem. The basic knowledge > of discrete mathematics that allows me to count that has been > indispensible, in my experience. I never do that. I write the program and if it takes too long, I rewrite it. Much quicker than trying to struggle with mathematical analysis! L. - Automatic footer for [EMAIL PROTECTED] ---------------------------------- To unsubscribe from this list, mail [EMAIL PROTECTED] unsubscribe discuss To join the announcements list, mail [EMAIL PROTECTED] subscribe announce To receive a help file, mail [EMAIL PROTECTED] help This list is archived at http://www.mail-archive.com/discuss%40ppig.org/ If you have any problems or questions, please mail [EMAIL PROTECTED]
