Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use \cs_new_protected:Npn for expl3 functions not fully expandable #235

Open
muzimuzhi opened this issue Jun 19, 2023 · 1 comment
Open

Comments

@muzimuzhi
Copy link
Contributor

To ease expansion handling, expl3 follows the rule that a function is either fully expandable or protected.

As of v6.0.5 only two zlabel-related functions are defined by \cs_new_protected:Npn, which will eventually be defined with prefix \protected. More non-expandable functions should be created by \cs_new_protected:Npn and \cs_new_protected_nopar:Npn, not the corresponding \cs_new:Npn and \cs_new_nopar:Npn.

@T-F-S
Copy link
Owner

T-F-S commented Jun 19, 2023

I take this as some general advice when overhauling code.

@muzimuzhi muzimuzhi changed the title Use \cs_new_protected:Npn when needed Use \cs_new_protected:Npn for un-expandable expl3 functions Sep 8, 2024
@muzimuzhi muzimuzhi changed the title Use \cs_new_protected:Npn for un-expandable expl3 functions Use \cs_new_protected:Npn for expl3 functions not fully expandable Sep 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants