References: <b82e8c205ad01b9f6e95b8c482ce192873f2070e.camel@sipsolutions.net>
            <bd4e695d-79ac-249f-5f85-2e8b1832c183@morningstar2.co.uk>
            <0bd9377ae896d7b54baa292a2f7b6e4254f4ec13.camel@sipsolutions.net>
            <58B049B2-2617-4C21-930F-1DF862106E4C@wspr.io>
            <d279ef6668d7ad397d32bf14b1917898de826500.camel@sipsolutions.net>
            <99C6DD7E-0A4E-44E1-A7F7-9756F5C41821@wspr.io>
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
            Thunderbird/52.9.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Message-ID:  <d29f83de-893a-456e-8f21-214b1ea60dd5@morningstar2.co.uk>
Date:         Mon, 27 Aug 2018 08:19:12 +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:         Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: \ior_get_str:NN vs. \ior_str_get:NN
To:           LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <99C6DD7E-0A4E-44E1-A7F7-9756F5C41821@wspr.io>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Content-Transfer-Encoding: 8bit
Status: R

On 27/08/2018 07:52, Will Robertson wrote:
> On 27 Aug 2018, at 1:28 pm, Benjamin Berg <benjamin@SIPSOLUTIONS.NET> wrote:
>>
>> However, while this worked fine with older LaTeX distributions, the
>> user with a newer distribution reported the following error:
>>
>>    Runaway argument?
>>    {\cs_new_eq:NN \ior_str_get:NN
>>    ! Forbidden control sequence found while scanning use of \use_i:nn.
> 
> Ah, deprecated commands are defined to be \outer. That’s rather awkward… I don’t think there’s a real easy way around it then!

Ah, but there is:

     \cs_if_exist:NF \ior_str_get:NN
       { \cs_set_eq:Nc \ior_str_get:NN { ior_get_str:NN } }

i.e. the usual trick for using \outer macros inside something else.

That should work, but note that there's a reason we've 'forced the 
issue' here: expl3 is still evolving, and we want to make sure we don't 
end up with a totally nightmare in terms of macro usage.

Joseph