Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
References: <b82e8c205ad01b9f6e95b8c482ce192873f2070e.camel@sipsolutions.net>
            <bd4e695d-79ac-249f-5f85-2e8b1832c183@morningstar2.co.uk>
            <0bd9377ae896d7b54baa292a2f7b6e4254f4ec13.camel@sipsolutions.net>
Message-ID:  <58B049B2-2617-4C21-930F-1DF862106E4C@wspr.io>
Date:         Mon, 27 Aug 2018 13:12:53 +0930
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:         Will Robertson <will@WSPR.IO>
Subject: Re: \ior_get_str:NN vs. \ior_str_get:NN
To:           LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <0bd9377ae896d7b54baa292a2f7b6e4254f4ec13.camel@sipsolutions.net>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Content-Transfer-Encoding: 8bit
Status: R

Hi Benjamin,

> On 27 Aug 2018, at 12:38 pm, Benjamin Berg <benjamin@SIPSOLUTIONS.NET> wrote:
> 
> The problem for me is that I am shipping the package separately, which
> means that I am confronted with whatever version the user already has
> on their machine.

If you really know that users will be updating/using new versions of your package on outdated systems, and they can’t/won't upgrade l3kernel itself, the best/easiest thing to do in this case would be to have code like:

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

(Perhaps with a warning in there that if at all possible the user should update their expl3 version.) And then use the updated version of the command.

Regards,
Will