MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <A0EC36FA-07DB-4D5B-B652-487C829D1D93@yahoo.de>
            <4B59B86F.8070007@morningstar2.co.uk>
            <06B4B7DE-4CBE-41AB-85F4-B81B120D858C@yahoo.de>
            <4B59BD1F.7090000@morningstar2.co.uk>
Message-ID:  <19289.49290.171302.534731@morse.mittelbach-online.de>
Date:         Fri, 22 Jan 2010 16:13:14 +0100
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@listserv.uni-heidelberg.de>
Sender: Mailing list for the LaTeX3 project <LATEX-L@listserv.uni-heidelberg.de>
From: Frank Mittelbach <frank.mittelbach@LATEX-PROJECT.ORG>
Subject: Re: Collision between mathtools.sty and expl3
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <4B59BD1F.7090000@morningstar2.co.uk>
Precedence: list
Status: R

Joseph Wright writes:
 > On 22/01/2010 14:51, Philipp Stephani wrote:
 > >> This is because Morten's stuff has up to now used it's own expl3-like stuff internally. The team as a whole can't change things, unless of course Morten deputises the job to someone!
 > >
 > > Well, you could simply change the definitions to use \cs_set_eq:NN for the moment.
 > > The main problem with such collisions is that it creates unnecessary work for users or package writers who want to use expl3 or xparse.
 > 
 > I should have been a bit clearer: I meant that expl3 is "correct" here, 
 > the change needs to be with mhsetup. Something will get sorted over the 
 > weekend :-)

if the two would work together by just using \cs_set_eq:NN for the moment then
as a short measure we could do that until mhsetup gets sorted out. However, it
might be the case that more is needed given that the mhsetup code is only
"based on" expl3 concepts but was used to run standalone and was developed
when expl3 was in an earlier stage.

as Joseph said, we should sort it out one way or the other soon.

frank