Linux Creator Torvalds Details Code Differences
Linux Creator Torvalds Details Code Differences
The SCO Group Inc. recently made some specific claims about programs within Linux that it contends were stolen from the Lindon, Utah, companys Unix intellectual property. Linux founder Linus Torvalds on Monday offered eWEEK.com a number of specific code examples that countered SCOs assesment.
Here are some specific areas where Torvalds found differences between Unix and Linux:
Torvalds looked at lib/ctype.c and include/linux/ctype.h.
"First, some background: The ctype name comes character type, and the whole point of ctype.h and ctype.c is to test what kind of character were dealing with," Torvalds said.
"In other words, those files implement tests for doing things like asking, is this character a digit or is this character an uppercase letter etc.
"So you can write something like:
.. we do something with the digit ...
and the ctype files implement that logic."
"Those files exist (in very similar form) in the original Linux-0.01 release under the names lib/ctype.c and include/ctype.h. That kernel was released in September of 1991, and contains no code except for mine and Lars Wirzenius, who co-wrotekernel/vsprintf.c."
"In fact, you can look at the files today and 12 years ago, and you can see clearly that they are largely the same: the modern files have been cleaned up and fix a number of really ugly things (tolower/toupper works properly), but they are clearly incremental improvement on the original one."
Torvalds added that original Linux version did not look like the Unix source one. He said it had several similarities that he attributed to the following reasons:
- The ctype interfaces are defined by the C standard library.
- The C standard also specifies what kinds of names a system-library interface can use internally. In particular, the C standard specifies that names that start with an underscore and a capital letter are internal to the library.
This is important, Torvalds said, because it explains why both the Linux implementation and the Unix implementation used a particular naming scheme for the flags.
- Algorithmically, there arent many ways to test whether a character is a number or not. Thats especially true in C, where a macro must not use its argument more than once.
Torvalds provided an example: "The obvious implementation of isdigit(), which tests for whether a character is a digit or not) would be:
#define isdigit(x) ((x) >= 0 && (x) <= 9)
but this is not actually allowed by the C standard, because x is used twice."
"This explains why both Linux and traditional Unix use the other obvious implementation: having an array that describes what each of the possible 256 characters are, and testing the contents of that array (indexed by the character) instead. That way the macro argument is only used once," Torvalds said.
"This basically explains the similarities. There simply arent that many ways to do a standard C ctype implementation, in other words," he said.
Torvalds went on to "look at the differences between Linux and traditional Unix."
"Both Linux and traditional Unix use a naming scheme of underscore and a capital letter for the flag names. There are flags for is upper case (_U) and is lower case (_L), and surprise, surprise, both Unix and Linux use the same name," Torvalds said.
"But think about itif you wanted to use a short flag name, and you were limited by the C-standard naming, what names would you use? Maybe youd select U for Upper case and L for Lower case?"
"Looking at the other flags, Linux uses _D for Digit, while traditional Unix instead uses _N for Number. Both make sense, but they are different," he continued.
"I personally think that the Linux naming makes more sense (the function that tests for a digit is called isdigit(), not isnumber()), but on the other hand, I can certainly understand why Unix uses _Nthe function that checks for whether a character is alphanumeric is called isalnum(), and that checks whether the character is a upper case letter, a lower-case letter or a digit (a k a, number)."
"In short: there arent that many ways you can choose the names, and there is lots of overlap, but its clearly not 100 percent," Torvalds said.
More Code Examples
"The original Linux ctype.h/ctype.c file has obvious deficiencies, which pretty much point to somebody new to C making mistakes(me) rather than any old and respected source," Torvalds observed.
"For example, the toupper()/tolower() macros are just totally broken, and nobody would write the isascii() and toascii() the way they were written in that original Linux. And you can see that they got fixed later on in Linux development, even though you can also see that the files otherwise didnt change," he said.
"Remember how C macros must only use their argument once. So lets say that you wanted to change an upper-case character into a lower-case one, which is what tolower() does. Normal use is just a fairly obvious:
newchar = tolower(oldchar)
"And the original Linux code does:
extern char _ctmp;
"This is not very pretty, but notice how we have a temporary character _ctmp (remember that internal header names should start with an underscore and an upper case characterthis is already slightly broken in itself). Thats there so that we can use the argument c only onceto assign it to the new temporaryand then later on we use that temporary several times," he said.
Torvalds said the reasons this is broken are:
- Its not thread-safe. "If two different threads try to do this at once, they will stomp on each others temporary variable."
- The argument might be a complex expression, and as such it should really be parenthesized, he said. The above example "gets several valid (but unusual) expressions wrong."
According to Torvalds, these are the kinds of mistakes a young programmer would make. "Its classic," he said.
"And I bet its not what the Unix code looked like, even in 1991. Unix by then was 20 years old, and I think that it uses a simple table lookup (which makes a lot more sense anyway and solves all problems)," he suggested. "Id be very surprised if it had those kinds of beginner mistakes in it, but I dont actually have access to the code, so what do I know? I can look up some BSD code on the Web, it definitely does not do anything like the above," he continued.
Torvalds added that the lack of proper parentheses existed in other places of the original Linux ctype.h file. He said isascii() and toascii() were similarly broken.
"In other words: There are lots of indications that the code was not copied, but was written from scratch. Bugs and all," he said.
Torvalds said he had recently searched Google for the term _ctmp. He said the results were Linux-related. "Doing a Google search for _ctmp -linux shows more Linux pages that just dont happen to have Linux in them, except for one which is the L4 microkernel. And that one shows that they used the Linux header file [since] it still says _LINUX_CTYPE_H in it."
"There is definitely a lot of proof that my ctype.h is original work," Torvalds said.