categories - Category Theory list
 help / color / mirror / Atom feed
From: Steve Stevenson <steve@cs.clemson.edu>
To: Categories List <categories@mta.ca>
Subject: Question on standard terminology
Date: Mon, 6 Oct 2003 09:31:41 -0400	[thread overview]
Message-ID: <6B79B655-F801-11D7-A52E-000A959EB774@cs.clemson.edu> (raw)

Good Morning:

I have a question about "standard terminology" or "standard
methodology". Is there a standard technique to generate the closure of
a set through generating the next element from the current? The
motivating idea is a simple one: generate a free language from the list
of characters. This is a standard inductive process seen in lots of
automata and formal language books. Seems like there is product
followed by a co-product sort of action.

best regards,

steve
--------
D. E. Stevenson, Department of Computer Science
Clemson University, Clemson, SC 29634-0974
864.656.6880 http://www.cs.clemson.edu/~steve






                 reply	other threads:[~2003-10-06 13:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6B79B655-F801-11D7-A52E-000A959EB774@cs.clemson.edu \
    --to=steve@cs.clemson.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).