问题描述
传统的汇编程序和更高级别的编译器根据预期用途使用多个内存段。因此，存在一个数据段，一个堆栈段，一个bss和文本段。文本段也称为代码段。
Traditional assembler, and higher level compilers work with several memory segments, according to intended use. Hence, there is a data segment, a stack segment, a bss, and text segment. The text segment is also called the code segment.
文本段？对于机器代码？
我问过我能找到的所有旧定时器，怎么知道像机器代码这样不易理解的东西文本段。他们每个人都同意那确实是它的名字，但是似乎没有人对此感到惊讶。没人能提供解释。
I have asked all the old-timers I could find, how something as unreadable as machine code came to be know as the "text segment". Every one of them agreed that, that was really what it was called, but none of them seemed to be surprised by it. And no one could offer an explanation.
这是您的机会，通过启发我们来炫耀您的极客历史知识。
Here's your chance to show off your geek history knowledge by enlightening us.
推荐答案
再加上nos的评论，我打开了，并在宏汇编器的部分中找到以下内容：
Going a little further with nos's comments, I turned up a scanned version of the GE-635 Programming Manual, and found the following in the section on the macro assembler:
因此，二进制文本的使用似乎是通用语言，或者是当时的常用术语（请记住，那是读卡器/打孔机被用于许多IO的日子。 ）。因此，一种可能的途径是GE，通过GE-645到达Multics，通过Bell Labs在Multics上的工作到达Unix，再到Linux。
So, it appears that the use of "binary text" was a GE colloquialism, or perhaps a commonly used term at the time (remember that those were the days when card readers/punches were used for much IO). So, one possible path is GE, to Multics via GE-645, to Unix via Bell Labs' work on Multics, to Linux.
这篇关于文本段在哪里获得的名称？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！