Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Turing machine continuity w/ other definitions #221

Open
BassP97 opened this issue Dec 28, 2019 · 1 comment
Open

Turing machine continuity w/ other definitions #221

BassP97 opened this issue Dec 28, 2019 · 1 comment

Comments

@BassP97
Copy link

BassP97 commented Dec 28, 2019

Hi all! Sipser (and other TOC sources) use a 7-tuple definition of a turing machine:

  1. Start State
  2. Reject State
  3. Accept state
  4. Transition function
  5. Tape Alphabet
  6. Input alphabet
  7. Set of states

The open logic chapter on computation, in contrast, uses a 4-tuple definition. Is there a reason for this (maybe a difference in philosophy/computer science's respective disciplinary norms?) or should I (or someone else) rewrite the definition using the more conventional 7-tuple?

@BassP97 BassP97 changed the title Turinig machine continuity w/ other definitions Turing machine continuity w/ other definitions Dec 28, 2019
@rzach
Copy link
Member

rzach commented Dec 28, 2019

There is no single universally accepted definition. Eg, the OLP definition uses a one-sided tape and a tape-end marker, and allows the tape head to not move (so it is like the definition in Papadimitriou's Complexity Theory, for instance). Since the OLP (as of yet, in any case) has no content that would require separate input and tape alphabets, or a baked-in requirement that every machine has an accept and a reject state, I don't think that's necessary or useful. The sections comparing definitions could be expanded though. Let's keep the simpler definition for now, I'd say.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants