LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: \ior_get_str:NN vs. \ior_str_get:NN
From:
Will Robertson <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Mon, 27 Aug 2018 13:12:53 +0930
Content-Type:
text/plain
Parts/Attachments:
text/plain (18 lines) 
Hi Benjamin,

> On 27 Aug 2018, at 12:38 pm, Benjamin Berg <[log in to unmask]> 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

ATOM RSS1 RSS2