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












2















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























  • 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
    5 hours ago











  • expandafterdefcsname macro2endcsname{command output} is valid syntax. You then must use it via csname macro2endcsname.

    – Steven B. Segletes
    5 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
    5 hours ago
















2















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























  • 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
    5 hours ago











  • expandafterdefcsname macro2endcsname{command output} is valid syntax. You then must use it via csname macro2endcsname.

    – Steven B. Segletes
    5 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
    5 hours ago














2












2








2


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?






macros environments







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




macros environments






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 5 hours ago









U. WindlU. Windl

1597




1597













  • 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
    5 hours ago











  • expandafterdefcsname macro2endcsname{command output} is valid syntax. You then must use it via csname macro2endcsname.

    – Steven B. Segletes
    5 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
    5 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
    5 hours ago











  • expandafterdefcsname macro2endcsname{command output} is valid syntax. You then must use it via csname macro2endcsname.

    – Steven B. Segletes
    5 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
    5 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
5 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
5 hours ago













expandafterdefcsname macro2endcsname{command output} is valid syntax. You then must use it via csname macro2endcsname.

– Steven B. Segletes
5 hours ago







expandafterdefcsname macro2endcsname{command output} is valid syntax. You then must use it via csname macro2endcsname.

– Steven B. Segletes
5 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
5 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
5 hours ago










1 Answer
1






active

oldest

votes


















5














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 begin{tabular} accesses tabular but begin{tabular*} 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









    5














    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 begin{tabular} accesses tabular but begin{tabular*} 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






























      5














      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 begin{tabular} accesses tabular but begin{tabular*} 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




























        5












        5








        5







        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 begin{tabular} accesses tabular but begin{tabular*} 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 begin{tabular} accesses tabular but begin{tabular*} 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 4 hours ago









        Phelype Oleinik

        24.9k54690




        24.9k54690










        answered 4 hours ago









        David CarlisleDavid Carlisle

        497k4111441891




        497k4111441891






























            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







            -

            Popular posts from this blog

            Ponta tanko

            Image
            Usona ponta tanko M60A1 Ponta tanko estas, simile kiel kirasita savveturilo, inter specialaj kirasitaj transportiloj. Kiel pontaj tankoj eblas konsideri ĉiujn memmovigaj rimedoj ebligantaj superi obstaklojn ĝis larĝeco 24 metroj rekte en spaco de bataloperacoj. Ties ĉefa tasko estas ebligi al la propraj taĉmentoj daŭrigi en rapida antaŭenirado sen senbezona reteniĝo. El tio pli-malpli rezultas taktikaj-teknikaj postuloj, kiujn ili devas plenumi. Precipe temas pri kapablo operacii komune kun unue-sinsekvaj taĉmentoj kaj transpontigi obstaklojn dum kelke da minutoj. This page is only for reference, If you need detailed information, please check here
            Read more

            Tantalo (mitologio)

            Image
            Ĉi tiu artikolo temas pri mitologio. Por aliaj signifoj vidu la paĝon Tantalo (apartigilo) . Tantalo , laŭ Gioacchino Assereto. Laŭ la helena mitologio, Tantalo (el la greka Τάνταλος , ŝancelanta aŭ tre malfeliĉa ) estis filo de Zeŭso kaj la oceanidino Pluto, laŭ la plej divastigata versio. Li estis reĝo de Frigio [1] aŭ de la monto Sipilo, en Lidio (Malgrandazio) [2] kaj post sia morto li suferis eternan torturadon ĉe la Tartaro, la plej profunda parto de Hadeso, rezervita por la plej perversaj homoj. Tamen, kelkaj rakontoj asertas ke li estis reĝo de Argo aŭ de Korinto [3] , aŭ ke li migris norden el la monto Sipilo por akiri la tronon de Paflagonio, el kie Ilo forpelis lin pro tio, ke Tantalo forkaptis kaj seksperfortis lian fraton Ganimedon [4] , kaj tiel ofendis la diojn. Verŝajne li ankaŭ regis urbon en okcidenta Anatolio, kiun oni nomis Tantalis [5] pro li, aŭ Sipilo , pro la monto sur kies flanko ankoraŭ staras ĝiaj ruinaĵoj [6] . Laŭ la geografiisto Strabo,...
            Read more

            Erzsébet Schaár

            Image
            Erzsébet Schaár Memportreto de Erzsébet Schaár en Pécs Personaj informoj Naskiĝo 27-an de julio 1908 ( 1908-07-27 ) en Budafok Morto 29-an de aŭgusto 1975 ( 1975-08-29 ) (67-jara) en Budapeŝto Ŝtataneco Hungario Profesio skulptisto Familianoj Edz(in)o Tibor Vilt v   •   d   •   r Erzsébet Schaár [erĵEbet ŝAr], laŭ hungarlingve kutima sinsekvo Schaár Erzsébet estis hungara skulptisto. Ŝia edzo estis Tibor Vilt. Déryné Széppataki Róza en Miskolc fare de Erzsébet Schaár Erzsébet Schaár [1] naskiĝis la 27-an de julio 1908 en Budafok, ŝi mortis la 29-an de aŭgusto 1975 en Budapeŝto. Enhavo 1 Biografio 2 Elektitaj solaj ekspozicioj 3 Elektitaj kolektivaj ekspozicioj 4 Elektitaj skulptaĵoj 5 Elektitaj disĉiploj 6 Fontoj 7 Referencoj Biografio | Erzsébet Schaár studis en Industriarta Lernejo, poste en Reĝa Belarta Altlernejo (1924-1926). Ŝia ĉefinstruisto estis Zsig...
            Read more