Dragonfall
- 1,023
- 5
Can someone prove to me why computable numbers are not closed under the taking of suprema?
The discussion revolves around the properties of computable numbers, specifically whether they are closed under the taking of suprema. Participants explore definitions and implications related to computable sets and their characteristics in the context of computable analysis.
Participants do not reach a consensus on the definitions of computable sets or the closure properties of computable numbers under suprema. Multiple competing views and uncertainties remain throughout the discussion.
Limitations include the lack of fixed definitions for computable sets and the unresolved nature of the implications of these definitions on the properties of computable numbers.
Sorry, I left the adjective "computable" implicit.CRGreathouse said:(2) seems to have serious problems (how to input a real number? how to operate on it in a finite amount of time?).
Hurkyl said:Sorry, I left the adjective "computable" implicit.
But we're not talking about "recognizing a real number". We're talking about "doing a calculation with a computable real number". To be computable presupposes we have a way to write the number a finite string of symbols, and the TM would be programmed to operate on such representations.Dragonfall said:I think CRGreathouse means that it is not possible to recognize a real number with a TM, which can only regonize finitely many symbols, and strings of finite length.
It could be stronger, but it doesn't need to be; it's a definition, and it has properties. It may be useful for some purpose, or it might not.Dragonfall said:(1) needs to be stronger. The TM must list those that are in the set, and those that aren't (say, in alternating order). It's the "recursive" vs. "recursively enumerable" thing all over again.