LaTeX: Why are digits allowed in environments, but forbidden in commands?What exactly do csname and endcsname do?Why are some characters not allowed in command sequencesWhy does LaTeX make a distinction between commands and environments?Do all starred commands have anything in common?Why are some characters not allowed in command sequencesSuggestions for an automatic taxonomy environmentUse a character other than the backslash for commandsWhy are LaTeX macros so inconsistent?Are end… macro names reserved in LaTeX2e?Can't use command with square brackets in matrix environmentHow to control conditional statements within new commands and environmentsCreating Commands which Make New Environments

Multi tool use
Multi tool use

Has there ever been an airliner design involving reducing generator load by installing solar panels?

Why does Kotter return in Welcome Back Kotter?

How to draw a waving flag in TikZ

Paid for article while in US on F-1 visa?

Which country benefited the most from UN Security Council vetoes?

Can a Cauchy sequence converge for one metric while not converging for another?

Doing something right before you need it - expression for this?

Replacing matching entries in one column of a file by another column from a different file

Is it tax fraud for an individual to declare non-taxable revenue as taxable income? (US tax laws)

Modeling an IP Address

How does quantile regression compare to logistic regression with the variable split at the quantile?

"You are your self first supporter", a more proper way to say it

RSA: Danger of using p to create q

Theorems that impeded progress

Why is consensus so controversial in Britain?

tikz convert color string to hex value

What's the point of deactivating Num Lock on login screens?

Today is the Center

Why are electrically insulating heatsinks so rare? Is it just cost?

Is it inappropriate for a student to attend their mentor's dissertation defense?

How can bays and straits be determined in a procedurally generated map?

Does an object always see its latest internal state irrespective of thread?

What's the output of a record needle playing an out-of-speed record

Meaning of に in 本当に



LaTeX: Why are digits allowed in environments, but forbidden in commands?


What exactly do csname and endcsname do?Why are some characters not allowed in command sequencesWhy does LaTeX make a distinction between commands and environments?Do all starred commands have anything in common?Why are some characters not allowed in command sequencesSuggestions for an automatic taxonomy environmentUse a character other than the backslash for commandsWhy are LaTeX macros so inconsistent?Are end… macro names reserved in LaTeX2e?Can't use command with square brackets in matrix environmentHow to control conditional statements within new commands and environmentsCreating Commands which Make New Environments













3















Finding out that I can have an environment named env2, but no command cmd2, I read Why are some characters not allowed in command sequences, but still I wonder:



Why are digits allowed in environments, but forbidden in commands? In my understanding digits delimit command names (inherited from plain TeX), but why doesn't that restriction apply to environments? Wouldn't it have been more consistent to forbid digits in environment names as well?










share|improve this question






















  • You actually can use numbers in commands. If you do expandafterdefcsname mycommandwithanumber123456endcsname you'll define a command mycommandwithanumber123456. The environments are created using the csname...endcsname pair, so it's fine.

    – Phelype Oleinik
    6 hours ago











  • expandafterdefcsname macro2endcsnamecommand output is valid syntax. You then must use it via csname macro2endcsname.

    – Steven B. Segletes
    6 hours ago












  • So the answer is "There are not forbidden, but they have to be used in a special way. Still it's recommended not to use them."?

    – U. Windl
    6 hours ago















3















Finding out that I can have an environment named env2, but no command cmd2, I read Why are some characters not allowed in command sequences, but still I wonder:



Why are digits allowed in environments, but forbidden in commands? In my understanding digits delimit command names (inherited from plain TeX), but why doesn't that restriction apply to environments? Wouldn't it have been more consistent to forbid digits in environment names as well?










share|improve this question






















  • You actually can use numbers in commands. If you do expandafterdefcsname mycommandwithanumber123456endcsname you'll define a command mycommandwithanumber123456. The environments are created using the csname...endcsname pair, so it's fine.

    – Phelype Oleinik
    6 hours ago











  • expandafterdefcsname macro2endcsnamecommand output is valid syntax. You then must use it via csname macro2endcsname.

    – Steven B. Segletes
    6 hours ago












  • So the answer is "There are not forbidden, but they have to be used in a special way. Still it's recommended not to use them."?

    – U. Windl
    6 hours ago













3












3








3


1






Finding out that I can have an environment named env2, but no command cmd2, I read Why are some characters not allowed in command sequences, but still I wonder:



Why are digits allowed in environments, but forbidden in commands? In my understanding digits delimit command names (inherited from plain TeX), but why doesn't that restriction apply to environments? Wouldn't it have been more consistent to forbid digits in environment names as well?










share|improve this question














Finding out that I can have an environment named env2, but no command cmd2, I read Why are some characters not allowed in command sequences, but still I wonder:



Why are digits allowed in environments, but forbidden in commands? In my understanding digits delimit command names (inherited from plain TeX), but why doesn't that restriction apply to environments? Wouldn't it have been more consistent to forbid digits in environment names as well?







macros environments






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 6 hours ago









U. WindlU. Windl

1697




1697












  • You actually can use numbers in commands. If you do expandafterdefcsname mycommandwithanumber123456endcsname you'll define a command mycommandwithanumber123456. The environments are created using the csname...endcsname pair, so it's fine.

    – Phelype Oleinik
    6 hours ago











  • expandafterdefcsname macro2endcsnamecommand output is valid syntax. You then must use it via csname macro2endcsname.

    – Steven B. Segletes
    6 hours ago












  • So the answer is "There are not forbidden, but they have to be used in a special way. Still it's recommended not to use them."?

    – U. Windl
    6 hours ago

















  • You actually can use numbers in commands. If you do expandafterdefcsname mycommandwithanumber123456endcsname you'll define a command mycommandwithanumber123456. The environments are created using the csname...endcsname pair, so it's fine.

    – Phelype Oleinik
    6 hours ago











  • expandafterdefcsname macro2endcsnamecommand output is valid syntax. You then must use it via csname macro2endcsname.

    – Steven B. Segletes
    6 hours ago












  • So the answer is "There are not forbidden, but they have to be used in a special way. Still it's recommended not to use them."?

    – U. Windl
    6 hours ago
















You actually can use numbers in commands. If you do expandafterdefcsname mycommandwithanumber123456endcsname you'll define a command mycommandwithanumber123456. The environments are created using the csname...endcsname pair, so it's fine.

– Phelype Oleinik
6 hours ago





You actually can use numbers in commands. If you do expandafterdefcsname mycommandwithanumber123456endcsname you'll define a command mycommandwithanumber123456. The environments are created using the csname...endcsname pair, so it's fine.

– Phelype Oleinik
6 hours ago













expandafterdefcsname macro2endcsnamecommand output is valid syntax. You then must use it via csname macro2endcsname.

– Steven B. Segletes
6 hours ago






expandafterdefcsname macro2endcsnamecommand output is valid syntax. You then must use it via csname macro2endcsname.

– Steven B. Segletes
6 hours ago














So the answer is "There are not forbidden, but they have to be used in a special way. Still it's recommended not to use them."?

– U. Windl
6 hours ago





So the answer is "There are not forbidden, but they have to be used in a special way. Still it's recommended not to use them."?

– U. Windl
6 hours ago










1 Answer
1






active

oldest

votes


















7














The restriction is in the scanner, tex's "eyes" in the texbook terminology. Any sequence of characters may be used as a command name, however after a character of catcode 0 (normally ) then tex scans the next non-letter (character of catcode other than 11) or a contiguous sequence of letters, and tokenizes it as a single csname token.



This means that foo123 normally parses as the token foo followed by the three tokens 1, 2, 3. Unless you make digits catcode 11. Similarly section* is normally the token section followed by the token *.



environment names use do not require to parse the name via the escape character, (they use the csname primitive but that's an implementation detail so begintabular accesses tabular but begintabular* accesses the command with name tabular* (not the two tokens that would normally be generated by parsing tabular*).



So technically it would be quite hard to not allow digits (or other characters) in environment names, especially when latex was designed there was not the memory available to add that kind of character-by-character check.






share|improve this answer

























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "85"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f483440%2flatex-why-are-digits-allowed-in-environments-but-forbidden-in-commands%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    7














    The restriction is in the scanner, tex's "eyes" in the texbook terminology. Any sequence of characters may be used as a command name, however after a character of catcode 0 (normally ) then tex scans the next non-letter (character of catcode other than 11) or a contiguous sequence of letters, and tokenizes it as a single csname token.



    This means that foo123 normally parses as the token foo followed by the three tokens 1, 2, 3. Unless you make digits catcode 11. Similarly section* is normally the token section followed by the token *.



    environment names use do not require to parse the name via the escape character, (they use the csname primitive but that's an implementation detail so begintabular accesses tabular but begintabular* accesses the command with name tabular* (not the two tokens that would normally be generated by parsing tabular*).



    So technically it would be quite hard to not allow digits (or other characters) in environment names, especially when latex was designed there was not the memory available to add that kind of character-by-character check.






    share|improve this answer





























      7














      The restriction is in the scanner, tex's "eyes" in the texbook terminology. Any sequence of characters may be used as a command name, however after a character of catcode 0 (normally ) then tex scans the next non-letter (character of catcode other than 11) or a contiguous sequence of letters, and tokenizes it as a single csname token.



      This means that foo123 normally parses as the token foo followed by the three tokens 1, 2, 3. Unless you make digits catcode 11. Similarly section* is normally the token section followed by the token *.



      environment names use do not require to parse the name via the escape character, (they use the csname primitive but that's an implementation detail so begintabular accesses tabular but begintabular* accesses the command with name tabular* (not the two tokens that would normally be generated by parsing tabular*).



      So technically it would be quite hard to not allow digits (or other characters) in environment names, especially when latex was designed there was not the memory available to add that kind of character-by-character check.






      share|improve this answer



























        7












        7








        7







        The restriction is in the scanner, tex's "eyes" in the texbook terminology. Any sequence of characters may be used as a command name, however after a character of catcode 0 (normally ) then tex scans the next non-letter (character of catcode other than 11) or a contiguous sequence of letters, and tokenizes it as a single csname token.



        This means that foo123 normally parses as the token foo followed by the three tokens 1, 2, 3. Unless you make digits catcode 11. Similarly section* is normally the token section followed by the token *.



        environment names use do not require to parse the name via the escape character, (they use the csname primitive but that's an implementation detail so begintabular accesses tabular but begintabular* accesses the command with name tabular* (not the two tokens that would normally be generated by parsing tabular*).



        So technically it would be quite hard to not allow digits (or other characters) in environment names, especially when latex was designed there was not the memory available to add that kind of character-by-character check.






        share|improve this answer















        The restriction is in the scanner, tex's "eyes" in the texbook terminology. Any sequence of characters may be used as a command name, however after a character of catcode 0 (normally ) then tex scans the next non-letter (character of catcode other than 11) or a contiguous sequence of letters, and tokenizes it as a single csname token.



        This means that foo123 normally parses as the token foo followed by the three tokens 1, 2, 3. Unless you make digits catcode 11. Similarly section* is normally the token section followed by the token *.



        environment names use do not require to parse the name via the escape character, (they use the csname primitive but that's an implementation detail so begintabular accesses tabular but begintabular* accesses the command with name tabular* (not the two tokens that would normally be generated by parsing tabular*).



        So technically it would be quite hard to not allow digits (or other characters) in environment names, especially when latex was designed there was not the memory available to add that kind of character-by-character check.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 5 hours ago









        Phelype Oleinik

        24.9k54690




        24.9k54690










        answered 5 hours ago









        David CarlisleDavid Carlisle

        497k4111441892




        497k4111441892



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f483440%2flatex-why-are-digits-allowed-in-environments-but-forbidden-in-commands%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            HWeC a70frtW,gpcGZwEx9dk,iMkoTmvExYe lCNAMY,qILLN2K,o
            lNZxCQlpgAhJsh xeDEVsx81hNxpkt3ELGzRp6e6,ww7bGm

            Popular posts from this blog

            Typsetting diagram chases (with TikZ?) Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)How to define the default vertical distance between nodes?Draw edge on arcNumerical conditional within tikz keys?TikZ: Drawing an arc from an intersection to an intersectionDrawing rectilinear curves in Tikz, aka an Etch-a-Sketch drawingLine up nested tikz enviroments or how to get rid of themHow to place nodes in an absolute coordinate system in tikzCommutative diagram with curve connecting between nodesTikz with standalone: pinning tikz coordinates to page cmDrawing a Decision Diagram with Tikz and layout manager

            SQL Server 2016 - excessive memory grant warning on poor performing query The Next CEO of Stack OverflowFix for slow SQL_INLINE_TABLE_VALUED_FUNCTIONLarge memory grant requestsPoor performing Query -Tsql execution plan - estimated number of rows =1 Paste the PlanMSSQL - Query had to wait for memory grantRow estimates always too lowBad performance using “NOT IN”Warning about memory “Excessive Grant” in the query plan - how to find out what is causing it?Optimizing table valued function SQL ServerWhen does SQL Server warn about an Excessive Memory Grant?Warning in Execution Plan

            What is the result of assigning to std::vector::begin()? The Next CEO of Stack OverflowWhat are the differences between a pointer variable and a reference variable in C++?What does the explicit keyword mean?Concatenating two std::vectorsHow to find out if an item is present in a std::vector?Why is “using namespace std” considered bad practice?What is the “-->” operator in C++?What is the easiest way to initialize a std::vector with hardcoded elements?What is The Rule of Three?What are the basic rules and idioms for operator overloading?Why are std::begin and std::end “not memory safe”?