Date: Tue, 18 Feb 2020 14:27:38 +0100 From: Joerg Schilling <joerg.schill...@fokus.fraunhofer.de> Message-ID: <5e4be64a.b7iehtvuvp4jwlze%joerg.schill...@fokus.fraunhofer.de>
| The problem here is that it is forbidden to create a function | with a name that is equal to a keyword. Yes, I knew that. | Since POSIX does not forbid to have keywords that are beyond the list from | POSIX, Hmm - POSIX allows lots of extenstions, but if that were true, then the only way to ever write a portable script would be to quote every command name, and there would be no way to ever define a function. XCU 2.4 goes to great lengths to list the reserved words, some other words that have to be treated as if they were reserved (just in case) and all words ending with a colon ... the latter two sets would not be needed if scripts were required to treat every word as if it might be reserved. I kind os suspect that the vast majority of sh script writers would be kind of amazed by this revelation. kre