categories - Category Theory list
 help / color / mirror / Atom feed
From: Vaughan Pratt <pratt@cs.stanford.edu>
To: categories list <categories@mta.ca>
Subject: Re: "Kantor dust"
Date: Wed, 11 Feb 2009 01:01:28 -0800	[thread overview]
Message-ID: <E1LXFOr-0003bY-4r@mailserv.mta.ca> (raw)


Prof. Peter Johnstone wrote on Feb. 7 at 17:18 GMT:
> The reason is that you have to know in advance that a binary
> sequence isn't going to end in an infinite string of 1's; by excluding
> those sequences, you make the question "Is x < 1/2?" decidable,
> which is not constructively true of either the Cantor reals or the
> Dedekind reals.

I had always been somewhat dissatisfied intuitively by the idea of
excluding sequences of the form 01111....  It seemed more natural to
identify them with those of the form 10000....  However I just assumed
that these were equivalent approaches.

Your point about making x < 1/2 decidable is a good one.  I'm now
convinced that it is better to identify than delete.  Identification can
be accomplished spatially, but perhaps it is more elegant to do so
localically, namely by removing the open set that separates the two
halves to be glued together.  In a T0 space, doing so will identify the
points anyway.  However in the situation [0,1)[1,2) of my previous
messages where there is no point on the left adjacent to the point 1 on
the right, identification of points is not an option.  The only
remaining concern then is whether there's an open set separating [0,1)
and [1,2).  Finality should eliminate spurious open sets that have no
reason to stick around.

Vaughan




             reply	other threads:[~2009-02-11  9:01 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11  9:01 Vaughan Pratt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-13  5:40 Vaughan Pratt
2009-02-12  9:05 Bas Spitters
2009-02-12  9:00 Prof. Peter Johnstone
2009-02-12  4:25 Toby Bartels
2009-02-12  4:10 Toby Bartels
2009-02-12  4:05 Toby Bartels
2009-02-11 23:51 Vaughan Pratt
2009-02-11 22:16 Bhupinder Singh Anand
2009-02-11 19:56 Greg Meredith
2009-02-11 17:53 Vaughan Pratt
2009-02-11 17:33 Prof. Peter Johnstone
2009-02-11 16:11 Michael Shulman
2009-02-11 15:55 Toby Kenney
2009-02-11  9:01 Vaughan Pratt
2009-02-11  5:49 Vaughan Pratt
2009-02-11  0:13 Toby Bartels
2009-02-10 22:18 Prof. Peter Johnstone
2009-02-10 21:05 Greg Meredith
2009-02-10 19:04 Steve Stevenson
2009-02-10  9:54 Vaughan Pratt
2009-02-09 22:47 Prof. Peter Johnstone
2009-02-09 22:18 Dusko Pavlovic
2009-02-09  1:30 Toby Bartels
2009-02-09  0:31 Toby Bartels
2009-02-08 20:36 Steve Stevenson
2009-02-08 15:03 Paul Taylor
2009-02-08 14:51 Prof. Peter Johnstone
2009-02-08 11:56 gcuri
2009-02-07 22:58 Toby Bartels
2009-02-07 17:18 Prof. Peter Johnstone
2009-02-07  0:37 Vaughan Pratt
2009-02-05 21:44 Toby Bartels
2009-02-04 20:24 Vaughan Pratt
2009-02-03 17:59 Prof. Peter Johnstone
2009-02-02 23:43 Vaughan Pratt
2009-02-01 18:53 Prof. Peter Johnstone
2009-02-01  0:06 Vaughan Pratt
2009-01-31 10:25 spitters
2009-01-31  4:35 Galchin, Vasili
2009-01-30 22:40 Galchin, Vasili
2009-01-30 21:52 Bas Spitters
2009-01-30  7:18 Galchin, Vasili
2009-01-30  7:18 Galchin, Vasili

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1LXFOr-0003bY-4r@mailserv.mta.ca \
    --to=pratt@cs.stanford.edu \
    --cc=categories@mta.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).