Will Robertson

I think Joseph was quite involved in the redevelopment of datatool’s backend. Since Nicola is quite active it might be worth discussing with her as well. A question I’d have...

What about a version of \file_input:n with arbitrary setup/closedown code? E.g., \file_input:nnn {code.tex} {\ExplSyntaxOff} {\ExplSyntaxOn}

For more context, here is the complete listing from xunicode-addon.sty: \cs_new_protected:Npn \__xunadd_reload:N #1 { \cs_set_eq:NN \__xunadd_tmp:w \iftipaonetoken \cs_set_eq:NN \iftipaonetoken \scan_stop: \use:x { \ExplSyntaxOff \char_set_catcode_letter:n { 64 } \exp_not:N \clist_map_function:NN \exp_not:N...

This seems like a reasonable argument to me to differentiate between \use:c and \cs_use:c...

Why is that an issue? Isn’t it orthogonal to the case at hand? I’m not sure, incidentally, why we couldn't have a \cs_new:N to precede \cs_set… To me the request...

IMO the proposed \cs_use:c with a check isn’t the same as \cs_if_exist_use:c — what I (and the OP I suspect) would find useful is a command which throws an error...

FWIW I've started implementing some of the changes outlined in some broader discussion around this issue. I'll make it public for discussion once I've ironed out some wrinkles and checked...

I just realised I am now years behind trying to complete this change. I got stalled when my pull request no longer cleanly merged :) I will try to get...

I’m surprised by the order of the arguments — under the int module shouldn’t the first arg be the int being tested? (Esp. If there is an N variant.) I...

I am happy with this `:)`