MIME-Version: 1.0
References: <CACKZBPXyV+Sv6ttKCKQcdccNcq330BD7XtJWGtuXHTtX00TsnA@mail.gmail.com> <54033B96.8070007@morningstar2.co.uk>
            <CACKZBPXf+mOtgboYZm9oOaqKoZA584z22WTexAaoAUdPiR627g@mail.gmail.com> <54037E00.9050005@latex-project.org>
            <CACKZBPUFSZE2Ux=pEeLHQdkEQZqMYPv_OTOHhDnpwFFDt=5j3A@mail.gmail.com> <54057A1B.4040605@latex-project.org>
            <CACKZBPUb=j-Hh95B51+dAEMJqsAtnUA_z+v+vo2CXGQR0QrH_A@mail.gmail.com>
            <54058E3F.7010605@latex-project.org>
Content-Type: text/plain; charset=UTF-8
Message-ID:  <CACKZBPW6ZCUd0OSZGaw9tLU6wQpz_G-HM+rYL2-QAp0DE7OijA@mail.gmail.com>
Date:         Tue, 2 Sep 2014 12:03:38 +0200
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: Michiel Helvensteijn <mhelvens@GMAIL.COM>
Subject: Re: How to get l3str.sty, l3seq.sty, etc. these days?
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <54058E3F.7010605@latex-project.org>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

On Tue, Sep 2, 2014 at 11:30 AM, Mittelbach, Frank
<frank.mittelbach@latex-project.org> wrote:

>> Even an error message that explains the situation would be preferable
>> to the standard "File `l3prop.sty' not found" error.
>
> ok that's probably better than a warning. Error  and explaining what to
> change, followed by loading expl3 so that the document can continue

That seems sensible. Users have probably (and justifiably) become
desensitized to console-warnings.

-- 
www.mhelvens.net