categories - Category Theory list
 help / color / mirror / Atom feed
From: Baruch Garcia <baruchgarcia@gmail.com>
To: Gershom B <gershomb@gmail.com>
Cc: Mike Stay <metaweta@gmail.com>, categories <categories@mta.ca>
Subject: Re: The use-mention distinction and category theory
Date: Tue, 26 Sep 2017 14:17:38 -0500	[thread overview]
Message-ID: <E1dxMZ1-0003eD-LM@mlist.mta.ca> (raw)
In-Reply-To: <CAM8RHpFX-L8TWmfef71v_NgH4wvtmrp+3GuQrUK4qCNV8bZ5Ug@mail.gmail.com>

Thanks, Gershom.

While Lawvere correctly points out that some try to misuse Godel's theorem,
I disagree with his *philosophical *perspective of the equivalence of
Cantor's diagonal argument and Godel's diagonal lemma.  The former does not
employ the use-mention distinction while the latter does.  This is what
gives rise to the "paradoxical" nature of Godel's theorem.  Please read
Quine's "The Ways of Paradox" for more.

Regardless, Lawvere's approach to Godel and Tarski provides an important
bridge between computer science and category theory.

Best,
BG

On Tue, Sep 26, 2017 at 12:00 PM, Gershom B <gershomb@gmail.com> wrote:

> I would suggest that one approach to the use-mention distinction is
> given in topos theory, or more generally in categorical logic, when we
> can talk about the "internal logic" of a category, and discuss objects
> of categories from both the internal and external standpoints.
>
> A common case of this arises in Mike's message when he discusses the
> internal hom. Godel, Halting, etc. all can be seen as statements based
> on a particular structure surrounding the internal hom as in [1].
>
> [1] https://ncatlab.org/nlab/show/Lawvere%27s+fixed+point+theorem
>
> Cheers,
> Gershom
>
> On Tue, Sep 5, 2017 at 1:36 PM, Mike Stay <metaweta@gmail.com> wrote:
>> On Sun, Sep 3, 2017 at 1:19 PM, Baruch Garcia <baruchgarcia@gmail.com>
> wrote:
>>> Hello,
>>>
>>> I was wondering if someone of the categories list could answer this
>>> question:
>>>
>>> In Godel's/Tarski's theorem and the Halting problem, the use-mention
>>> distinction (e.g. Boston is populous, but "Boston" is disyllabic) is
>>> essential.  Is there an analog to the use-mention distinction in
> category
>>> theory or is the use-mention distinction just its own principle
> independent
>>> of category theory?
>>
>> There's something like a distinction between use and mention in a
>> symmetric monoidal closed category.  Given a morphism f:X -> Y,
>> there's the "name" of the function curry(f):I -> X -o Y, where I is
>> the monoidal unit and -o is the internal hom.  The evaluation morphism
>> takes a value g of type X -o Y and a value x of type X and returns
>> uncurry(g)(x).
>>
>>
>> --
>> Mike Stay - metaweta@gmail.com
>> http://www.cs.auckland.ac.nz/~mike
>> http://reperiendi.wordpress.com
>>

[For admin and other information see: http://www.mta.ca/~cat-dist/ ]


      parent reply	other threads:[~2017-09-26 19:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-03 19:19 Baruch Garcia
2017-09-05  5:46 ` Patrik Eklund
2017-09-05 17:36 ` Mike Stay
2017-09-26 17:00   ` Gershom B
     [not found]   ` <CAM8RHpFX-L8TWmfef71v_NgH4wvtmrp+3GuQrUK4qCNV8bZ5Ug@mail.gmail.com>
2017-09-26 19:17     ` Baruch Garcia [this message]

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=E1dxMZ1-0003eD-LM@mlist.mta.ca \
    --to=baruchgarcia@gmail.com \
    --cc=categories@mta.ca \
    --cc=gershomb@gmail.com \
    --cc=metaweta@gmail.com \
    /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).