Sfrgttk

Why is 150k or 200k jobs considered good when there's 300k+ births a month?

If human space travel is limited by the G force vulnerability, is there a way to counter G forces?

How much RAM could one put in a typical 80386 setup?

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

How do I deal with an unproductive colleague in a small company?

High voltage LED indicator 40-1000 VDC without additional power supply

What are these boxed doors outside store fronts in New York?

Can I make popcorn with any corn?

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

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

Is it legal for company to use my work email to pretend I still work there?

What would happen to a modern skyscraper if it rains micro blackholes?

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

Could an aircraft fly or hover using only jets of compressed air?

What's that red-plus icon near a text?

What does "Puller Prush Person" mean?

What doth I be?

Are astronomers waiting to see something in an image from a gravitational lens that they've already seen in an adjacent image?

dbcc cleantable batch size explanation

What does it mean to describe someone as a butt steak?

What is a clear way to write a bar that has an extra beat?

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

Do I have a twin with permutated remainders?

Unable to deploy metadata from Partner Developer scratch org because of extra fields

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

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

asked 2 hours ago

U. WindlU. Windl

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
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  expandafterdefcsname macro2endcsname{command output} is valid syntax. You then must use it via csname macro2endcsname.
  
  – Steven B. Segletes
  2 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
  2 hours ago
  

  
  
  
  

add a comment | 

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

asked 2 hours ago

U. WindlU. Windl

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
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  expandafterdefcsname macro2endcsname{command output} is valid syntax. You then must use it via csname macro2endcsname.
  
  – Steven B. Segletes
  2 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
  2 hours ago
  

  
  
  
  

add a comment | 

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

asked 2 hours ago

U. WindlU. Windl

1597

share|improve this question

asked 2 hours ago

U. WindlU. Windl

1597

share|improve this question

asked 2 hours ago

U. WindlU. Windl

1597

asked 2 hours ago

U. WindlU. Windl

1597

asked 2 hours ago

U. WindlU. Windl

1597

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

edited 1 hour ago

Phelype Oleinik

24.9k54690

answered 2 hours ago

David CarlisleDavid Carlisle

497k4111441891

add a comment | 

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

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

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

Name

Email

Required, but never shown

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

edited 1 hour ago

Phelype Oleinik

24.9k54690

answered 2 hours ago

David CarlisleDavid Carlisle

497k4111441891

add a comment | 

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

edited 1 hour ago

Phelype Oleinik

24.9k54690

answered 2 hours ago

David CarlisleDavid Carlisle

497k4111441891

add a comment | 

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

edited 1 hour ago

Phelype Oleinik

24.9k54690

answered 2 hours ago

David CarlisleDavid Carlisle

497k4111441891

share|improve this answer

edited 1 hour ago

Phelype Oleinik

24.9k54690

answered 2 hours ago

David CarlisleDavid Carlisle

497k4111441891

edited 1 hour ago

Phelype Oleinik

24.9k54690

edited 1 hour ago

Phelype Oleinik

24.9k54690

answered 2 hours ago

David CarlisleDavid Carlisle

497k4111441891

answered 2 hours ago

David CarlisleDavid Carlisle

497k4111441891