You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- 1"It is possible to model a single OOP object as finite state machine". True, but weak. It's not "possible". It's a matter of definition. A programming language's job is to express an FSM in a tidy notation. OOP is an implementation of an FSM with simpler notation for all the various states.S.Lott– S.Lott2011-07-22 11:22:56 +00:00Commented Jul 22, 2011 at 11:22
- 1@S.Lott - Yes, but most people don't think of an OOP object as expressing an FSM, at least not most of the time. Using the name "state machine" tends to imply that you're using some specific implementation, such as the state design pattern or a state-ID member variable. "Modelling as a state machine" often also implies something about the specification or design documentation, distinct from the implementation of that class. Therefore, modelling a class as a finite state model subjectively means something other than just providing the source code for the class.user8709– user87092011-07-22 11:34:48 +00:00Commented Jul 22, 2011 at 11:34
- "people don't think". True. And a deep problem. All programs are state machines. They have a lot of states. That's what the "Turing Complete" test for a programming language requires. It's a very, very strong (and absolute) rule. Rather than suggest it's "possible", it's more like "necessary" and "sufficient".S.Lott– S.Lott2011-07-22 11:37:49 +00:00Commented Jul 22, 2011 at 11:37
- 1-1: Push-down automata are NOT as powerful as Turing machines.kevin cline– kevin cline2014-06-02 17:54:10 +00:00Commented Jun 2, 2014 at 17:54
- 1@kevin cline - thanks - and what was I thinking!!! Edited to strike that bit out. Despite what I said about formal study, I know better than that and should have known better back then.user8709– user87092014-06-03 16:15:49 +00:00Commented Jun 3, 2014 at 16:15
| Show 5 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you