Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <199910011527.LAA04020@hilbert.math.albany.edu>
            <199910281728.SAA15046@mimosa.csv.warwick.ac.uk>
Message-ID:  <14361.50640.53971.453945@n15ux24.nets.de.eds.com>
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@URZ.UNI-HEIDELBERG.DE>
In-Reply-To:  <199910281728.SAA15046@mimosa.csv.warwick.ac.uk>
Date:         Fri, 29 Oct 1999 18:05:36 +0200
From: Frank Mittelbach <frank.mittelbach@SMC.EDS.DE>
Sender: Mailing list for the LaTeX3 project
              <LATEX-L@URZ.UNI-HEIDELBERG.DE>
To: Multiple recipients of list LATEX-L
              <LATEX-L@URZ.UNI-HEIDELBERG.DE>
Subject:      collection instances
Status: R

James Kilfiger writes:

 > On another matter, how will collection instances be used? Will
 > environments select a collection.  Would it be useful if \begin{myenv}
 > implictly called \UseCollection{myenv}.  You could use this to prohibit
 > sectional headings in floats, or \item outside of lists.  Would this be
 > within the expected use of collections.

 must confess we don't know that yet. we don't know eve if collection
instances are such a good idea in the first place. it is something
that will sort itself out probably pretty soon if we have played
around a bit with them.

i personally think that envs setting the collection instances is not
the way to go. when i played around with ists i tried doing this but
it didn't felt right.

as i said i don't know

frank